Marty Hernandez Avedon
0a7c7e7230
* 1172-refresh-helm-charts-in-rancher-page * wording revised, steps compressed * smoothing instructions, syncing language in similar steps * updated heading levels * versioning * versioned headings * Apply suggestions from code review Co-authored-by: Lucas Saintarbor <lucas.saintarbor@suse.com> * rm'd br tag, revised descr of project/namespace filter, made all nouns plural to match verb * Apply suggestions from code review missed one Co-authored-by: Lucas Saintarbor <lucas.saintarbor@suse.com> * Helm apps > Kubernetes apps * h3 heading and moved feature charts section * absolute link to older docs, spacing * heading levels * reorganizing/renaming helm charts in rancher section * rename some headings * changing path to apps/repositories to instead go through explore button * once > after * engineers say the default branch is set by the remote repo. Rancher will respect whatever that default is unless you specifically tell it to pull from another branch * straggler * fix in-page links after heading changed * wrong verb! * hyphen * moved section up as to not interrupt flow * moved info about upstream charts * moved line 64 to part of line 31 * Apply suggestions from code review Co-authored-by: Billy Tat <btat@suse.com> * Update versioned_docs/version-2.8/how-to-guides/new-user-guides/helm-charts-in-rancher/helm-charts-in-rancher.md Co-authored-by: Billy Tat <btat@suse.com> * Update versioned_docs/version-2.8/how-to-guides/new-user-guides/helm-charts-in-rancher/helm-charts-in-rancher.md Co-authored-by: Billy Tat <btat@suse.com> * Update versioned_docs/version-2.7/how-to-guides/new-user-guides/helm-charts-in-rancher/helm-charts-in-rancher.md Co-authored-by: Billy Tat <btat@suse.com> * Update versioned_docs/version-2.7/how-to-guides/new-user-guides/helm-charts-in-rancher/helm-charts-in-rancher.md Co-authored-by: Billy Tat <btat@suse.com> * Update docs/how-to-guides/new-user-guides/helm-charts-in-rancher/helm-charts-in-rancher.md Co-authored-by: Billy Tat <btat@suse.com> * Update docs/how-to-guides/new-user-guides/helm-charts-in-rancher/helm-charts-in-rancher.md Co-authored-by: Billy Tat <btat@suse.com> * Apply suggestions from code review Co-authored-by: Billy Tat <btat@suse.com> --------- Co-authored-by: Lucas Saintarbor <lucas.saintarbor@suse.com> Co-authored-by: Billy Tat <btat@suse.com>
10 KiB
title
| title |
|---|
| Helm Charts and Apps |
In this section, you'll learn how to manage Helm chart repositories and applications in Rancher.
How Helm Charts Work in Rancher
Rancher uses a catalog-like system to import bundles of charts from repositories and then uses those charts to either deploy custom Kubernetes applications or Rancher's tools such as Monitoring or Istio. Rancher tools come as pre-loaded repositories which deploy as standalone Helm charts. Any additional repositories are only added to the current cluster.
Catalogs, Apps, and the Rancher UI
Rancher v2.4 and earlier, repositories of ready-to-deploy applications were called "catalogs". These repositories were managed through the Catalogs section of the UI.
Helm chart repositories are now managed using Apps & Marketplace (before Rancher v2.6.5) or Apps (Rancher v2.6.5 and later).
Versioning Changes in Rancher v2.6
Starting in Rancher v2.6.0, a new versioning scheme for Rancher feature charts was implemented. The changes are centered around the major version of the charts and the +up annotation for upstream charts, where applicable.
Major Version: The major versions of feature charts are tied to Rancher minor versions. When you upgrade to a new Rancher minor version, you should ensure that all of your charts are also upgraded to the correct release line for the chart.
Charts based on upstream: When you upgrade, make sure that the upstream chart version is compatible with your Rancher version. The +up annotation for the chart indicates which upstream version the Rancher chart is tracking. For example, 100.x.x+up16.6.0 for Monitoring tracks upstream kube-prometheus-stack 16.6.0 with some additional Rancher patches.
When upgrading Rancher versions, don't downgrade the version of the chart that you are using. For example, if you are using a version of Monitoring that is later than 16.6.0 in Rancher v2.5, you shouldn't upgrade to 100.x.x+up16.6.0. Instead, you should upgrade to the appropriate version in the next release.
:::note
Any major versions that are less than the ones mentioned in the table below are meant for 2.5 and below only. For example, you are advised to not use <100.x.x versions of Monitoring in 2.6.x+.
:::
Feature Charts
| Name | Supported Minimum Version | Supported Maximum Version |
|---|---|---|
| external-ip-webhook | 100.0.0+up1.0.0 | 100.0.1+up1.0.1 |
| harvester-cloud-provider | 100.0.2+up0.1.12 | 100.0.2+up0.1.12 |
| harvester-csi-driver | 100.0.2+up0.1.11 | 100.0.2+up0.1.11 |
| neuvector | 100.0.0+up2.2.0 | 100.0.0+up2.2.0 |
| rancher-alerting-drivers | 100.0.0 | 100.0.2 |
| rancher-backup | 2.0.1 | 2.1.2 |
| rancher-cis-benchmark | 2.0.1 | 2.0.4 |
| rancher-gatekeeper | 100.0.0+up3.6.0 | 100.1.0+up3.7.1 |
| rancher-istio | 100.0.0+up1.10.4 | 100.3.0+up1.13.3 |
| rancher-logging | 100.0.0+up3.12.0 | 100.1.2+up3.17.4 |
| rancher-longhorn | 100.0.0+up1.1.2 | 100.1.2+up1.2.4 |
| rancher-monitoring | 100.0.0+up16.6.0 | 100.1.2+up19.0.3 |
| rancher-sriov (experimental) | 100.0.0+up0.1.0 | 100.0.3+up0.1.0 |
| rancher-vsphere-cpi | 100.3.0+up1.2.1 | 100.3.0+up1.2.1 |
| rancher-vsphere-csi | 100.3.0+up2.5.1-rancher1 | 100.3.0+up2.5.1-rancher1 |
| rancher-wins-upgrader | 0.0.100 | 100.0.1+up0.0.1 |
Access Charts
From the top-left menu select Apps and you will be taken to the Charts page.
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. You can filter charts by selecting the left-most dropdown menu:
- Rancher tools such as Logging or Monitoring are listed under the Rancher label.
- Partner charts are under the Partners label.
- Custom charts are listed under the name of their respective repository.
All three types of charts are deployed and managed in the same way.
:::note
Apps managed by the Cluster Manager (the global view in the legacy Rancher UI) should continue to be managed only by the Cluster Manager, and apps managed with Apps & Marketplace (Rancher before v2.6.5) or Apps (Rancher v2.6.5+) in the new UI must be managed only by Apps & Marketplace or Apps.
:::
Manage Repositories
The Repositories page lists your Helm repositories. These include traditional Helm endpoints which have an index.yaml, and Git repositories that are cloned and point to a specific branch. To use custom charts, add your repository here. After you add a repository, you can access custom charts in the Charts page, listed under the name of the repository.
To access the Repositories page, select Repositories from the left nevigation menu.
Add Custom Git Repositories
To add a custom Git repository that contains your Helm charts or cluster template definitions:
- Select Repositories from the left nevigation menu.
- Click Create.
- Select the target, Git repository containing Helm chart....
- You must enter a name and a Git repository URL. The other fields, including the description, are optional. Enter an alternative branch name if you don't want to pull from whichever branch the repo owner has set as the default. Usually, the default branch is named either
mainormaster. - Click Create to add the repository.
After you add a chart repository to Rancher, it becomes available immediately.
Add Custom Helm Chart Repositories
You can add your own Helm chart repositories to serve chart packages to Rancher. You can use any HTTP server, as long as the server can respond to GET requests and serve YAML files and tar archives.
For more information on Helm chart repositories, see the official Helm docs.
- Select Repositories from the left nevigation menu.
- Click Create.
- Select the target, http(s) URL to an index generated by Helm.
- Enter a repo name and the index URL address of the chart repository.
Add Private Git/Helm Chart Repositories
You can add private Git or Helm chart repositories with SSH key credentials or an HTTP basic auth secret, such as a username and password.
Add a Private CA to Repositories
To add a private CA to Helm chart repositories:
- Select Repositories from the left nevigation menu.
- Find the row associated with the Git or HTTP-based repository you want to add a private CA to, and click ⋮ > Edit YAML.
- Set the
caBundlevalue, as in the following example:
[...]
spec:
caBundle:
MIIFXzCCA0egAwIBAgIUWNy8WrvSkgNzV0zdWRP79j9cVcEwDQYJKoZIhvcNAQELBQAwPzELMAkGA1UEBhMCVVMxCzAJBgNVBAgMAkNBMRQwEgYDVQQKDAtNeU9yZywgSW5jLjENMAsGA1UEAwwEcm9vdDAeFw0yMTEyMTQwODMyMTdaFw0yNDEwMDMwODMyMT
...
nDxZ/tNXt/WPJr/PgEB3hQdInDWYMg7vGO0Oz00G5kWg0sJ0ZTSoA10ZwdjIdGEeKlj1NlPyAqpQ+uDnmx6DW+zqfYtLnc/g6GuLLVPamraqN+gyU8CHwAWPNjZonFN9Vpg0PIk1I2zuOc4EHifoTAXSpnjfzfyAxCaZsnTptimlPFJJqAMj+FfDArGmr4=
[...]
:::note Helm chart repositories with authentication
As of Rancher v2.6.3, a new value disableSameOriginCheck has 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 spec portion of the YAML file, add disableSameOriginCheck and set it to true.
[...]
spec:
disableSameOriginCheck: true
[...]
:::
Helm Compatibility
Only Helm 3 compatible charts are supported.
Deploy and Upgrade Charts
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. After 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 features. These pages include links to dashboards, forms to easily add Custom Resources, and additional information.
:::caution
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 after they are created. To ensure you do not get this error you can:
- Use the default upgrade option ( i.e do not use
--forceoption ). - Uninstall the existing chart and install the upgraded chart.
- Delete the resources with immutable fields from the cluster before performing the
--forceupgrade.
:::
Changes in Rancher v2.6.3
The upgrade button isn't available for legacy apps on the Apps > Installed Apps page.
If you want to upgrade an installed legacy app, the legacy feature flag must be turned on. This flag is automatically turned on if you had a legacy app already running before you upgraded Rancher.
- You can upgrade the app from cluster explorer, from the left nav section Legacy > Project > Apps.
- For multi-cluster apps, you can go to ≡ > Multi-cluster Apps and upgrade the app from there.
Limitations
Dashboard apps or Rancher feature charts can't be installed using the Rancher CLI.