This topic provides details on configuring Helm OCI to work with Artifactory. To get up and running quickly to use Helm OCI, see Get Started with Helm OCI.
Pre-requisite: Before connecting your Helm client to Artifactory, you must have an existing Helm OCI repository in Artifactory. For more information, see Create a Helm OCI Repository
Supported Helm OCI Clients
Helm version 3.8.0 or above
Note
These instructions are relevant for Helm OCI Repositories and intended for use with Helm client version 3.8.0 and later (or for prior versions with OCI Experimental mode enabled). Helm OCI repositories do not support non-OCI interactions. For more information, see the Helm documentation.
Logged in vs. Anonymous User: You can work with Artifactory as either a logged in user or as an anonymous user. To work with Artifactory using Anonymous Access. You need to configure that access under Admin | Security | General. For details, refer to Allow Anonymous Access.
To configure your local machine to install Helm OCI charts, follow these steps:
To configure the Helm OCI client with Artifactory, log in using the
helm registry logincommand:helm registry login https://[JFrogPlatformURL]Where:
[JFrogPlatformURL]: Your JPD name<USER_NAME>: Your JPD username<TOKEN>: Your JPD Token
Alternatively, you can provide your username and token in advance using the following command:
helm registry login -u <USER_NAME> -p <TOKEN> https://[JFrogPlatformURL]Note
Use Helm OCI With Older Client Versions
Starting from Artifactory version 7.75.3, to use Helm OCI with a Helm client version before 3.8.0, run this command in your Helm client:
export HELM_EXPERIMENTAL_OCI=1
Use an encrypted password
We recommend using an encrypted password instead of a clear-text. For details, please refer to Centrally Secure Passwords.
Note: You can also use JFrog Set me up to copy the snippet populated with your token and environment. For more information, see Use Artifactory Set Me Up for Configuring Package Manager Clients.
Note
When using Helm OCI repositories with a reverse proxy or load balancer, it is important to understand that the Docker access method configured in Artifactory directly impacts how Helm OCI repositories are accessed. This is true even if you are working exclusively with Helm OCI charts.
For instructions on configuring your reverse proxy for Helm OCI, refer this guide.
Next Steps: