Helm Management Guide
When you install a Helm chart, Helm creates a release. You can manage the release by updating, upgrading, or uninstalling it.
When you install a Helm chart, the Helm client creates an instance of the chart in your Kubernetes cluster. This instance is called a release, and Helm uses it to manage all of the objects and resources that the chart creates. When you deploy the Autonomous Operator or another component via the Couchbase Helm Chart, you will manage the deployed resources by making updates to the release in Helm.
The sections on this page describe how to manage the Helm releases that make up your deployments.
During the lifecycle of your deployment, it’s likely that you will want to make changes to your deployment’s configuration (e.g. add/remove nodes from a cluster, etc). To make configuration updates to a deployment, you’ll need to modify the release in Helm.
To modify a release, you’ll specify overrides via the --values or --set options much like you did when you installed the Couchbase Helm Chart to begin with.
However, when modifying a release, you use the
helm upgrade command instead of
helm upgrade --values myvalues.yaml <release-name> couchbase/couchbase-operator
It’s important that you make your updates using the
helm upgrade command instead of using
kubectl or simply editing chart resources.
This is to ensure that Helm can continue to update and manage all resources appropriately.
Upgrading the Autonomous Operator and Admission Controller to a newer version requires that you upgrade the release to a newer version of its chart. This allows Helm to ensure that all dependencies specified by the chart get updated appropriately.
helm upgrade --version <chart-version> <release-name> couchbase/couchbase-operator
<chart-version> is the version of the Couchbase Helm Chart that you want to upgrade to, and
<release-name> is the name of the release that is managing the instance of the Autonomous Operator that you wish to upgrade.
Refer to the Operator upgrade documentation for more information about the upgrade process.
It is not possible to upgrade the 1.2.x Autonomous Operator chart to 2.0.x. If you have a previous installation of the Autonomous Operator chart, you will need to delete the release, as well as delete the CRD.
If you didn’t originally install the Autonomous Operator using Helm, then you cannot upgrade the Autonomous Operator using Helm. At this time, installations of the Autonomous Operator that weren’t created with Helm cannot be ported over to using Helm.
There are two methods for upgrading a Couchbase cluster with Helm. The first method is to upgrade the release to a newer version of the Couchbase Helm Chart that uses the desired Couchbase Server version as a default. The second method is to update the existing release to use a newer Couchbase Server image. The first method is preferred, since upgrading the entire chart will ensure that any potential new parameters required to configure the cluster are defined.
|When upgrading a Couchbase cluster, you should first upgrade the Autonomous Operator to the latest compatible version so as to ensure that the cluster can be properly managed.|
Check the default Couchbase Server version of a chart to make sure that it uses the version that you want to upgrade your cluster to.
helm inspect --version <chart-version> values couchbase/couchbase-cluster | grep "version:"
<chart-version>is the version number of a newer chart.
Upgrade to the newer chart.
helm upgrade --version <chart-version> <release-name> couchbase/couchbase-cluster
<chart-version>is the version of the Couchbase Helm Chart that you want to upgrade to, and
<release-name>is the name of the release that is managing the Couchbase cluster that you wish to upgrade.
helm upgrade --set cluster.image=<image> <release-name> couchbase/couchbase-cluster
<image> is the name of the container image.
For example, to upgrade a cluster to Couchbase Server 6.5.1:
helm upgrade --set cluster.image=couchbase/server:6.5.1 <release-name> couchbase/couchbase-cluster