NetBackup™ Deployment Guide for Kubernetes Clusters

AKS-specific

1. Launch an Azure CLI pod into the AKS cluster using the following command:

   $ kubectl run az-cli --image=mcr.microsoft.com/azure-cli --command sleep infinity

   Note:

   Access to Azure Key Vault is restricted to specific subnets. Passwords stored in Azure Key Vault can be easily updated from a pod running in AKS.

2. Exec into the Azure CLI pod as follows:

   $ kubectl exec -it az-cli -- /bin/ash

3. From Azure CLI pod, log into Azure account:

   $ az login --scope https://graph.microsoft.com//.default

4. (Optional) Create a key vault policy to allow the current user to retrieve the database credential.

   Obtain the name of your resource group, key vault and ID of the current user by using the following respective commands:

   • Resource group name:

     $ RESOURCE_GROUP=<resource_group_name>

   • Key vault name:

     $ KEY_VAULT_NAME=$(az keyvault list --resource-group $RESOURCE_GROUP --resource-type vault | jq -r '.[].name')

   • Current user ID name:

     $ USER_ID=$(az account show | jq -r '.user.name')

   Create a key vault access policy as follows:

   $ az keyvault set-policy -n $KEY_VAULT_NAME --upn $USER_ID --resource-group $RESOURCE_GROUP --secret-permissions all

5. Obtain the login name for the key vault (DBADMINUSER):

   $ DBADMINUSER=$(az keyvault secret show --vault-name $KEY_VAULT_NAME --name dbadminlogin | jq -r .value)

6. Obtain the password for the key vault (OLD_DBADMINPASSWORD):

   $ OLD_DBADMINPASSWORD=$(az keyvault secret show --vault-name $KEY_VAULT_NAME --name dbadminpassword | jq -r .value)

7. Set the new password as follows:

   Before setting the new password ensure that you know your database server name or obtain it by using the following command:

   $ DBSERVER=$(az postgres flexible-server list --resource-group $RESOURCE_GROUP | jq -r '.[].name')

   Use the following command to set the new password:

   $ az postgres flexible-server execute -p $OLD_DBADMINPASSWORD -u $DBADMINUSER -n $DBSERVER -d postgres -q "ALTER USER\"nbdbadmin\" WITH PASSWORD '<new_password>';"

   Note:

   To install rdbms-connect extension, ensure that you select the Y option.

8. Use the following command to verify if the password is using the correct encryption method (SCRAM-SHA-256):

   $ az postgres flexible-server execute -p "<new_password>" -u $DBADMINUSER -n $DBSERVER -d postgres -q "SELECT * from azure_roles_authtype();"

   +---------------------------+-----------+
   | rolename                  | authtype  |
   |---------------------------+-----------|
   | azuresu                   | NOLOGIN   |
   | pg_database_owner         | NOLOGIN   |
   | pg_read_all_data          | NOLOGIN   |
   | pg_write_all_data         | NOLOGIN   |
   | pg_monitor                | NOLOGIN   |
   | pg_read_all_settings      | NOLOGIN   |
   | pg_read_all_stats         | NOLOGIN   |
   | pg_stat_scan_tables       | NOLOGIN   |
   | pg_read_server_files      | NOLOGIN   |
   | pg_write_server_files     | NOLOGIN   |
   | pg_execute_server_program | NOLOGIN   |
   | pg_signal_backend         | NOLOGIN   |
   | azure_pg_admin            | NOLOGIN   |
   | replication               | NOLOGIN   |
   | nbdbadmin                 | SCRAM-256 |
   +---------------------------+-----------+
   SELECT 15
   Time: 0.009s

9. Store the updated password in key vault:

   $ az keyvault secret set --vault-name $KEY_VAULT_NAME --name dbadminpassword --value "<new_password>"

10. (Optional) Delete the key vault access policy created in step 4 above:

    $ az keyvault delete-policy -n $KEYVAULT --upn $USER_ID

11. Exit from the azure CLI pod:

    $ exit

12. Delete the az CLI pod:

    $ kubectl delete pod az-cli

13. (Applicable only for an existing cloudscale deployment) Restart the primary pod:

    $ kubectl rollout restart "statefulset/${PRIMARY}" --namespace "${NAMESPACE}"

    In the above command,

    • NAMESPACE is the namespace containing your NetBackup deployment

    • PRIMARY is the name of primary pod's stateful set

    Use the following command to obtain NAMESPACE and PRIMARY:

    $ kubectl get --namespace "${NAMESPACE}" primaryserver -o jsonpath='{.items[0].status.attributes.resourceName}'

EKS-specific

1. Use lambda function to change the password.

   LAMBDA_ARN is the ARN of the password changing lambda function. This can be obtained from the lambda function page on AWS console.

   NEW_PASSWORD is the new password to be used.

   $ aws lambda invoke --function-name $LAMBDA_ARN \ --cli-binary-format raw-in-base64-out --payload '{"password":"$NEW_PASSWORD"}' \ response_file

2. Wait for database to be available.

   Obtain the POSTGRESQL_ID (database identifier)of your RDS Postgres database from the RDS database page of the AWS console, using the following command:

   $ aws rds wait db-instance-available --db-instance-identifier $POSTGRESQL_ID

3. Restart the primary pod:

   $ kubectl rollout restart "statefulset/${PRIMARY}" --namespace "${NAMESPACE}"

   In the above command,

   • NAMESPACE is the namespace containing your NetBackup deployment

   • PRIMARY is the name of primary pod's stateful set

   Use the following command to obtain NAMESPACE and PRIMARY:

   $ kubectl get --namespace "${NAMESPACE}" primaryserver -o jsonpath='{.items[0].status.attributes.resourceName}'