Add Rancher managed RKE cluster in NetBackup using automated configuration
Follow the steps to add Rancher managed RKE cluster in NetBackup using automated configuration.
To add Rancher managed RKE cluster in NetBackup using automated configuration
Note:
Extract the Global Rancher Management server certificate. This CA cert can be a default generated cert by rancher or configured by using a different/external CA (Certifying Authority) during the management servers creation.
- Extract the CA cert: Navigate to the Rancher Management Server UI> Open the left side panel Global Settings > Under CA Certs, click the Show CA Certs button. Extract the complete CA cert value in a temporary file.
Note:
Make sure you extract the complete value which includes the starting and ending lines.
- The CA certificate value is added in the secret which is created before Kubernetes operators helm install
- To Extract the token: Open the Rancher Management Server UI > Open the left side panel > Under the Explore Cluster Section > Navigate to the cluster you want to protect > Click the Download KubeConfig icon on the top right corner.
- Download the cluster's KubeConfig using the icon and the token field is present inside the file.
- Extract the token: value without the double quotes " " from this downloaded Kubeconfig file.
- This configuration process relies on a secret with the following naming pattern
(<kops-namespace>-nb-config-deploy-secret).The secret have the values that are extracted in steps 1 & 3.
- Create a yaml file
nb-config-deploy-secret. yamlwith the following format and enter the values in all the fields.apiVersion: v1 kind: secret metadata: name: <kops-namespce>-nb-config-deploy-secret namespace: <kops-namespace> type: Opaque stringData: #All the 3 fields are mandatory here to add a Rancher managed RKF2 cluster in NetBackup apikey: A_YoUkgYQwPLUkmyj9Q6A1-6RX8RNY-PtYX0SukbqCwIK-osPz8qVm9zCL9phje k8stoken: kubeconfig-user-mvvgcm8sq8:nrscvn8hj46t24r2tjrxd2kn8tzo2bg4kj8waxpw36k8ktrchp826 k8scacert: | -------BEGIN CERTIFICATE----- MIIDDDCCAfSgAwIBAgIBATANBgkqhkiG9w0BAQwIgYDVQQDDBtpbmdy ZXNzLW9wZXJhdG9yQDE2ODc1MzY4NjgWHhcNMjMwNjIzMTYxNDI3WhcNMjUwNjIy XtXqbaBGrXIuCCo90mxv4g== -------END CERTIFICATE------ - Run the command: kubectl apply -f nb-config-deploy-secret. yaml
- For the rest of the inputs in the values.yaml file of your helm chart refer the Automated Configuration section of the Kubernetes Quick Start guide and enter all the values which are necessary for a complete setup.
- Run Helm install command on the NetBackup Kubernetes operator chart if all the necessary simplified install inputs are added in the
values.yamlfile, and the automated configuration pod <kops-namespace>-netbackup-config-deploy should start up. - Observe the <kops-namespace>-netbackup-config-deploy logs to identify if the updated secret value is picked up by the config-deploy pod.
- Once the config-deploy pod performs its tasks the cluster is successfully added in NetBackup, and a discovery request is in progress or successfully completed. Perform another credential validation and manual discovery from the NetBackup web UI to ensure the process is working fine.