Enabling MSDP S3 service after MSDP Scaleout is deployed

If MSDP S3 service is not enabled during the initial deployment, you can enable it later.

Identify the MSDP Scaleout deployment method of your deployment. Some of the steps in this procedure differ based on the MSDP Scaleout deployment method.

MSDP Scaleout is deployed with environment YAML in the following scenarios:
- NetBackup and MSDP are deployed together in the same cluster
- Cloud Scale is deployment using the Terraform
- Cloud Scale is deployment using the Maketplace
MSDP Scaleout is deployed with MSDP Scaleout YAML in the following scenarios:
- NetBackup and MSDP are not deployed together in the same cluster

To enable MSDP S3 service

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 the cluster 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-<version>-0065/bin/kubectl-msdp /usr/local/bin/
Input S3 credential field and S3 IP/FQDN fields in existing CR resources.
- If the MSDP Scaleout is deployed with environment YAML, run the following command to update the spec.msdpScaleouts[<index>].s3Credential and spec.msdpScaleouts[<index>].s3Ip fields in the existing CR resources:
  $ kubectl edit environments.netbackup.veritas.com <environmentCR_name> -n <sample-namespace>
  Content format:
```
msdpScaleouts:

  - credential:
      autoDelete: true
      secretName: msdp-creds
      skipPrecheck: false

    s3Credential:
      secretName: <s3secretName>

 			s3Ip:
      ipAddr: <s3IpAddress>
      fqdn: <s3Fqdn>
```
- If the MSDP Scaleout is deployed with MSDP Scaleout YAML, run the following command to update the spec.s3Credential and spec.s3ServiceIPFQDN fields in the existing CR resources:
  $ kubectl edit msdpscaleouts.msdp.veritas.com.msdp.veritas.com <MSDP Scaleout CR name> -n <sample-namespace>
  Content format:
```
spec:

    credential:
      autoDelete: true
      secretName: msdp-creds
      skipPrecheck: false

    s3Credential:
      secretName: <s3secretName>

    s3ServiceIPFQDN:
      ipAddr: <s3IpAddress>
      fqdn: <s3Fqdn>
```
Provide the NetBackup token for MSDP S3.
If the MSDP Scaleout is deployed using helm command, skip this step. This step is done automatically by the environment operator.
If the MSDP Scaleout is deployed with MSDP Scaleout YAML, create a token from NetBackup web UI. Navigate to Security > Tokens > Add. Run the following command to create a token secret in Kubernetes:
$ kubectl create secret generic <S3-token-secret-name> --namespace <sample-namespace> --from-literal=token=<token-value>
Run the following command to update the spec.nbca.s3TokenSecret field in the existing CR resources:
$ kubectl edit msdpscaleout <MSDP Scaleout CR name> -n <sample-namespace>
Content format:
```
spec:
    nbca:
      s3TokenSecret: <S3-token-secret-name>
```
Wait for a few minutes. MSDP operator enables S3 service automatically.
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.

Enabling MSDP S3 service after MSDP Scaleout is deployed

Feedback

Feedback