Upgrade Velero and Datamover
Cohesity uses third-party software Velero 1.4 to back up and recover data at the namespace level.
If Kubernetes is not accessed through the internet, you must provide the path to the registry from which Velero should be pulled. For Cohesity Cluster version 7.2 and later, if Kubernetes is accessible from the internet, the Cohesity Kubernetes code will pull Velero version 1.12.2.
Configure Velero while Registering a Kubernetes Cluster
When you are registering the Kubernetes cluster as a source or re-registering a deleted Kubernetes cluster, on the Register Kubernetes Source page:
-
In the Velero Image field, enter the location of the Velero image saved in your Docker registry.
-
In the DataMover Image field, enter the location of the supported DataMover image saved in your Docker registry.
Upgrade Velero in Existing Kubernetes Cluster Sources
If you have existing Kubernetes Clusters registered with the Cohesity cluster, verify whether the Cohesity namespace is present or absent in the registered source. The procedure to upgrade Velero is different when the Cohesity namespace is present and when the Cohesity namespace is absent.
Verify if the Cohesity Namespace is Present
Run the following command on the master node of the Kubernetes cluster:
- kubectl get ns
Sample Output:
NAME | STATUS | AGE |
<auto-rec-jenkins-del | Active | 23h |
cohesity-21234567891234 | Active | 7d8h |
default | Active | 24d |
Jenkins | Active | 21d |
kube-node-lease | Active | 24d |
Kube-public | Active | 24d |
Kube-system | Active | 24d |
longhorn-system | Active | 20d |
mysql | Active | 12d |
wordpress | Active | 21d |
Verify if there are namespaces that have a unique suffix in their names within the command output. For example, cohesity-21234567891234
is the Cohesity namespace in the preceding sample.
Upgrade When Cohesity Namespace is Absent
If the Cohesity namespace is absent, no warnings or alerts are displayed in the Cohesity cluster regarding the requirement to upgrade Velero and Data Mover.
To upgrade Velero:
-
Run the following command on any node of the Kubernetes cluster (or from a node in another Kubernetes cluster that has access to the Kubernetes command-line tool) to delete the Velero Custom Resource Definition (CRD):
- kubectl delete crds -l component=velero
-
To edit the Kubernetes cluster source configuration:
-
Navigate to Data Protection > Sources.
-
Click the Actions menu (⋮) next to the Kubernetes cluster source and select Edit.
-
In the Register Kubernetes Source page, enter the locations of the new Velero and Data Mover images in the Datamover Image and Velero Image fields, respectively.
-
Click Register.
When registration is complete, a new entry appears on the Sources page.
-
Upgrade When the Cohesity Namespace is Present
If the Cohesity namespace is present in a registered Kubernetes cluster, a message is displayed in the Cohesity cluster indicating that you must upgrade the Cohesity data protection resources in the Kubernetes cluster. The message will also help you understand which Velero and Data Mover versions you must upgrade to.
To upgrade Velero:
-
Stop all the Kubernetes protection jobs that are currently running and ensure there are no active protection runs on the Kubernetes source.
-
Run the following command to delete the Cohesity namespace in the Kubernetes cluster:
- kubectl delete ns <name of the Cohesity namespace>
Example
- kubectl delete ns cohesity-21234567891234
-
Run the following command on any node of that Kubernetes cluster (or from a node in another Kubernetes cluster that has access to the Kubernetes command-line tool) to delete the Velero CRD:
- kubectl delete crds -l component=velero
-
To edit the Kubernetes cluster source configuration:
-
Navigate to Data Protection > Sources.
-
Click the Actions menu (⋮) next to the Kubernetes cluster source and select Edit.
-
In the Register Kubernetes Source page, enter the locations of the new Velero and Data Mover images in the Datamover Image and Velero Image fields, respectively.
-
Click Register.
When registration is complete, a new entry appears on the Sources page.
-