Upgrade Druva Backup Operator
You can upgrade Druva Backup Operator for Kubernetes clusters discovered from your AWS account and available on your CloudRanger console.
Note: During installation or upgrade, you may need to toggle between the terminal console and the Druva CloudRanger web console.
Step 1: Select cluster for DBO upgrade
-
To view your Kubernetes clusters, navigate to Resources > Kubernetes.
-
The Backup Operator Version displays DBO version for all registered clusters.
To upgrade the DBO version for a specific cluster, click Update.
Note: The Update option is only visible when new DBO versions are available.
Verify that the kubeconfig file is pointing to the appropriate cluster from the Terminal console and then proceed with executing the following helm commands.
Step 2: Update Druva Helm Charts
Execute the following commands to authorize Helm to fetch the charts repository:
-
Enable Open Container Initiative (OCI) support
Before authenticating with the Helm registry, set the following parameters:
export HELM_EXPERIMENTAL_OCI=1
Note: Currently OCI support is considered experimental. For more information, see Enabling OCI Support.
-
Authenticate with OCI registry (AWS ECR)
Once you have Helm ready, you can add a chart repository. To authenticate with the OCI registry, use the following format on terminal console:
aws ecr get-login-password --region <Region> | helm registry login --username AWS --password-stdin <Registry>
where,
Region indicates your AWS Region where the AWS ECR is located
Registry indicates the AWS ECR registry
-
Pull the following Helm charts
Once you authenticate the Helm charts, run the following commands to pull the charts for Druva Backup Operator and the applications that you wish to protect.
To pull charts for Druva backup CRDs, run the following command (mandatory):
helm chart pull <Registry>/backup.druva.com/charts/druva-backup-crds:<Chart_Tag>`
To pull charts for Druva Backup Operator, run the following command (mandatory):
helm chart pull <Registry>/backup.druva.com/charts/druva-backup-operator:<Chart_Tag>
To pull charts for specific applications, for example, a MySQL application (optional):
helm chart pull <Registry>/backup.druva.com/charts/druva-mysql-application:<Chart_Tag>`
where,
Registry indicates the AWS ECR registry
Chart Tag indicates the Helm chart tag
-
Export the following Helm charts
To export charts for Druva backup CRDs, run the following command (mandatory):
helm chart export <Registry>/backup.druva.com/charts/druva-backup-crds:<Chart_Tag>
To export charts for Druva Backup Operator, run the following command (mandatory):
helm chart export <Registry>/backup.druva.com/charts/druva-backup-operator:<Chart_Tag>
To export charts for specific applications, for example, a MySQL application (optional):
helm chart export <Registry>/backup.druva.com/charts/druva-mysql-application:<Chart_Tag>
where,
Registry indicates the AWS ECR registry
Chart Tag indicates the Helm chart tag
Step 3: Upgrade Backup CRDs
To upgrade charts for Druva backup CRDs, execute the following command:
helm upgrade druva-backup-crds./druva-backup-crds --namespace druva-system --create-namespace
Step 4: Upgrade Druva Backup Operator
Execute Helm commands to upgrade Druva Backup Operator and remove the selected cluster from Druva CloudRanger.
Note: You will need the Cluster URI and Cluster URL before executing the following Helm command on the terminal console. The registration token generated from the CloudRanger console will need to be provided to the Kubernetes Admin to be authenticated via CLI.
helm upgrade druva-backup-operator ./druva-backup-operator --namespace druva-system --create-namespace
--atomic --render-subchart-notes
--set bootstrap.clusterURI={CLUSTER_URI}
--set bootstrap.clusterURL={CLUSTER_URL}
--set druva-backup-config.nameOverride=druva-backup-config
--set global.image.registry=<Registry>
--set global.image.tag=<Image_Tag>
--set bootstrap.token=<Registration_Token>
--set catalogue.url=<CR_Catalogue_URL>
--set auth.rolearn=<Role ARN>
where,
Registration Token indicates the bootstrap token to authenticate your Kubernetes cluster with Druva CloudRanger
Image_Tag indicates the version of the image
Cluster_URL indicates the API Server endpoint of Kubernetes Cluster
Cluster_URI indicates the unique identifier for the Cluster
CR_Catalogue_URL indicates the CloudRanger catalogue endpoint for cluster registration
Role ARN indicates the Amazon Resource Name for the specific role, and is in the format:
arn:aws:iam::<AWS Account ID>:instance-profile/<Role name>
-
Once all commands are executed, click Update.
The Backup Operator Version will now display the latest DBO version for the selected cluster.