Using S3 service in MSDP Scaleout
Ensure that S3 credential secret field and S3 service IP/FQDN fields are updated in the environment YAML file or MSDP Scaleout CR YAML file.
See Enabling MSDP S3 service after MSDP Scaleout is deployed.
To use S3 service in MSDP Scaleout
- Check the S3 service status.
Run the following command to check if S3 service is configured or not:
$ kubectl get msdpscaleouts.msdp.veritas.com/<MSDP Scaleout CR name> -n <sample-namespace> -o=jsonpath={.status.s3srvConfigured}
If the command output is true, S3 service is configured and ready for use. Otherwise, wait for the flag to be true. The flag changes to true automatically after all MSDP Scaleout resources are ready.
- Use the following URL to access S3 service in MSDP Scaleout:
https://<MSDP-S3-FQDN>
Limitations:
S3 service in MSDP Scaleout only supports NBCA certificates.
You can use the CA certificate in NetBackup primary server to bypass SSL warnings when accessing S3 service. The CA certificate file path is
/usr/openv/var/webtruststore/cacert.pem.For example, when using AWS CLI you can use -ca-bundle parameter to specify CA certificate file path to bypass SSL warnings.
The region name of MSDP S3 service is the LSU name that is used to store S3 data. Set the default region name to PureDiskVolume to use the MSDP local LSU to store the S3 data.
Recommend 500~800 concurrent requests based on your Kubernetes node's performance.