NetBackup™ Deployment Guide for Kubernetes Clusters

To enable MSDP S3 service

1. Generate S3 root credential. Run the following command to generate the secret:

   $ kubectl msdp generate-s3-secret --namespace <sample-namespace> --s3secret <s3-secret-name>

   Ensure that you save the S3 credential at a secure place after it is generated for later use.

   If MSDP kubectl plug-in is not installed, copy MSDP kubectl plug-in from the operator TAR folder to a directory from where you access AKS host. This directory can be configured in the PATH environment variable so that kubectl can load MSDP kubectl as a plug-in automatically.

   For example,

   $ cp ./VRTSk8s-netbackup-10.2-0065/bin/kubectl-msdp /usr/local/bin/

2. Input S3 credential field in existing CR resources.

   • If the MSDP Scaleout is deployed with environment YAML, run the following command to update the spec.msdpScaleouts[<index>].s3Credential field in the existing CR resources:

     $ kubectl edit environment <environmentCR_name> -n <sample-namespace>

     Content format:

     msdpScaleouts:
     
       - credential:
     
           autoDelete: true
     
           secretName: msdp-creds
     
           skipPrecheck: false
     
         s3Credential:
     
           secretName: <s3secretName>

   • If the MSDP Scaleout is deployed with MSDP Scaleout YAML, run the following command to update the spec.s3Credential field in the existing CR resources:

     $ kubectl edit msdpscaleout <MSDP Scaleout CR name> -n <sample-namespace>

     Content format:

     spec:
     
       - credential:
     
           autoDelete: true
     
           secretName: msdp-creds
     
           skipPrecheck: false
     
         s3Credential:
     
           secretName: <s3secretName>

   Wait for a few minutes. MSDP operator enables S3 service automatically.

3. Run the following command to check the S3 service status:

   $ kubectl get msdpscaleouts.msdp.veritas.com/<MSDP Scaleout CR name> -o=jsonpath={.status.s3srvConfigured}

   If the command output is true, S3 service is configured and ready for use.

4. Before you start using S3 service, run the following command to restart pdde-s3srv service in the first MSDP engine:

   $ kubectl exec <first-MSDP-engine-FQDN> -n <sample-namespace> -c uss-engine -- systemctl restart pdde-s3srv