In this section, you'll learn how to manage Helm chart repositories and applications in Rancher.
Changes in Rancher v2.5
In Rancher v2.5, the Apps and Marketplace feature replaced the catalog system.
In the cluster manager, Rancher uses a catalog system to import bundles of charts and then uses those charts to either deploy custom helm applications or Rancher's tools such as Monitoring or Istio. The catalog system is still available in the cluster manager in Rancher v2.5, but it is deprecated.
Now in the Cluster Explorer, Rancher uses a similar but simplified version of the same system. Repositories can be added in the same way that catalogs were, but are specific to the current cluster. Rancher tools come as pre-loaded repositories which deploy as standalone helm charts.
From the top-left menu select "Apps & Marketplace" and you will be taken to the Charts page.
The charts page contains all Rancher, Partner, and Custom Charts.
- Rancher tools such as Logging or Monitoring are included under the Rancher label
- Partner charts reside under the Partners label
- Custom charts will show up under the name of the repository
All three types are deployed and managed in the same way.
Apps managed by the Cluster Manager should continue to be managed only by the Cluster Manager, and apps managed with the Cluster Explorer must be managed only by the Cluster Explorer.
From the left sidebar select "Repositories".
These items represent helm repositories, and can be either traditional helm endpoints which have an index.yaml, or git repositories which will be cloned and can point to a specific branch. In order to use custom charts, simply add your repository here and they will become available in the Charts tab under the name of the repository.
To add a private CA for Helm Chart repositories:
HTTP-based chart repositories: You must add a base64 encoded copy of the CA certificate in DER format to the spec.caBundle field of the chart repo, such as
openssl x509 -outform der -in ca.pem | base64 -w0. Click Edit YAML for the chart repo and set, as in the following example:
Git-based chart repositories: It is not currently possible to add a private CA. For git-based chart repositories with a certificate signed by a private CA, you must disable TLS verification. Click Edit YAML for the chart repo, and add the key/value pair as follows:
Note: Helm chart repositories with authentication
As of Rancher v2.5.12, a new value
disableSameOriginCheckhas been added to the Repo.Spec. This allows users to bypass the same origin checks, sending the repository Authentication information as a Basic Auth Header with all API calls. This is not recommended but can be used as a temporary solution in cases of non-standard Helm chart repositories such as those that have redirects to a different origin URL.
To use this feature for an existing Helm chart repository, click ⋮ > Edit YAML. On the
specportion of the YAML file, add
disableSameOriginCheckand set it to
The Cluster Explorer only supports Helm 3 compatible charts.
Deployment and Upgrades
From the "Charts" tab select a Chart to install. Rancher and Partner charts may have extra configurations available through custom pages or questions.yaml files, but all chart installations can modify the values.yaml and other basic settings. Once you click install, a Helm operation job is deployed, and the console for the job is displayed.
To view all recent changes, go to the "Recent Operations" tab. From there you can view the call that was made, conditions, events, and logs.
After installing a chart, you can find it in the "Installed Apps" tab. In this section you can upgrade or delete the installation, and see further details. When choosing to upgrade, the form and values presented will be the same as installation.
Most Rancher tools have additional pages located in the toolbar below the "Apps & Marketplace" section to help manage and use the features. These pages include links to dashboards, forms to easily add Custom Resources, and additional information.
If you are upgrading your chart using "Customize Helm options before upgrade" , please be aware that using the "--force" option may result in errors if your chart has immutable fields. This is because some objects in Kubernetes cannot be changed once they are created. To ensure you do not get this error you can:
- use the default upgrade option ( i.e do not use "--force" option )
- uninstall the existing chart and install the upgraded chart
- delete the resources with immutable fields from the cluster before performing the "--force" upgrade