NetBackup™ Deployment Guide for Kubernetes Clusters
- Introduction
- Section I. Configurations
- Prerequisites
- Prerequisites for Kubernetes cluster configuration
- Prerequisites for Cloud Scale configuration
- Recommendations and Limitations
- Configurations
- Configuration of key parameters in Cloud Scale deployments
- Prerequisites
- Section II. Deployment
- Section III. Monitoring and Management
- Monitoring NetBackup
- Monitoring Snapshot Manager
- Monitoring fluentbit
- Monitoring MSDP Scaleout
- Managing NetBackup
- Managing the Load Balancer service
- Managing PostrgreSQL DBaaS
- Managing logging
- Performing catalog backup and recovery
- Section IV. Maintenance
- PostgreSQL DBaaS Maintenance
- Patching mechanism for primary, media servers, fluentbit pods, and postgres pods
- Upgrading
- Cloud Scale Disaster Recovery
- Uninstalling
- Troubleshooting
- Troubleshooting AKS and EKS issues
- Troubleshooting AKS-specific issues
- Troubleshooting EKS-specific issues
- Troubleshooting AKS and EKS issues
- Appendix A. CR template
- Appendix B. MSDP Scaleout
- MSDP Scaleout configuration
- Managing MSDP Scaleout
- MSDP Scaleout maintenance
Prerequisites for using private registry
For registries requiring manual repository creation prior to pushing images, it is essential to set up the repositories in advance to ensure the successful pushing and pulling of images and Helm charts.
To deploy trust-manager using private registry
- Create kubernetes secret in trust-manager namespace using the following command:
kubectl create secret docker-registry demo-secret --namespace trust-manager --docker-server=nbk8s-bo.nbartifactory.rsv.ven.veritas.com --docker-username=<username_for_registry> --docker-password=<password_for_registry>
- Run the following command to download the helm chart:
helm repo add jetstack https://charts.jetstack.io
helm repo update
helm pull jetstack/trust-manager --version v0.6.0 (Download the Helm chart for trust-manager version v0.6.0 locally.)
- Push the required images to your private registry:
Note:
Ensure that the docker login is done for the private registry prior to pushing the images.
Syntax (pull, tag, push):
docker pull <source-registry>/<image-name>:<tag>
docker tag <source-registry>/<image-name>:<tag> <target-registry>/<image-name>:<tag>
docker push <target-registry>/<image-name>:<tag>
For example:
docker pull quay.io/jetstack/cert-manager-package-debian:20210119.0 docker tag quay.io/jetstack/cert-manager-package-debian:20210119.0 nbk8s-bo.nbartifactory.rsv.ven.veritas.com/cert-manager-package-debian:20210119.0 docker push nbk8s-bo.nbartifactory.rsv.ven.veritas.com/cert-manager-package-debian:20210119.0 docker pull quay.io/jetstack/trust-manager:v0.6.0 docker tag quay.io/jetstack/trust-manager:v0.6.0 nbk8s-bo.nbartifactory.rsv.ven.veritas.com/trust-manager:v0.6.0 docker push nbk8s-bo.nbartifactory.rsv.ven.veritas.com/trust-manager:v0.6.0
- Deploy trust-manager using the following command:
helm upgrade -i -n trust-manager trust-manager ./trust-manager-v0.6.0.tgz \
--set image.repository=nbk8s-bo.nbartifactory.rsv.ven.veritas.com/trust-manager \
--set image.tag=v0.6.0 \
--set imagePullSecrets[0].name=demo-secret \
--set app.trust.namespace=nbux \ --wait
- Run the following commands to list and verify if the trust-manager is installed:
helm list -n trust-manager
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION trust-manager trust-manager 1 <Date and Time> deployed trust-manager-v0.6.0 v0.6.0
kubectl get pods -n trust-manager
NAME READY STATUS RESTARTS AGE trust-manager-####47cc6c-949v6 1/1 Running 0 26m
To deploy cert-manager using private registry
- Create kubernetes secret in cert-manager namespace using the following command:
kubectl create secret docker-registry demo-secret --namespace cert-manager --docker-server=nbk8s-bo.nbartifactory.rsv.ven.veritas.com --docker-username=<username_for_registry> --docker-password=<password_for_registry>
- Run the following command to download the helm chart:
helm repo add jetstack https://charts.jetstack.io
helm repo update
helm pull jetstack/cert-manager --version 1.13.3 (Download the Helm chart for cert-manager version v1.13.3 locally.)
- Push the required images to your private registry:
Note:
Ensure that the docker login is done for the private registry prior to pushing the images.
Syntax (pull, tag, push):
docker pull <source-registry>/<image-name>:<tag>
docker tag <source-registry>/<image-name>:<tag> <target-registry>/<image-name>:<tag>
docker push <target-registry>/<image-name>:<tag>
For example,
docker pull quay.io/jetstack/cert-manager-controller:v1.13.3 docker pull quay.io/jetstack/cert-manager-webhook:v1.13.3 docker pull quay.io/jetstack/cert-manager-cainjector:v1.13.3 docker tag quay.io/jetstack/cert-manager-controller:v1.13.3 nbk8s-bo.nbartifactory.rsv.ven.veritas.com/cert-manager-controller:v1.13.3 docker tag quay.io/jetstack/cert-manager-webhook:v1.13.3 nbk8s-bo.nbartifactory.rsv.ven.veritas.com/cert-manager-webhook:v1.13.3 docker tag quay.io/jetstack/cert-manager-cainjector:v1.13.3 nbk8s-bo.nbartifactory.rsv.ven.veritas.com/cert-manager-cainjector:v1.13.3 docker push nbk8s-bo.nbartifactory.rsv.ven.veritas.com/cert-manager-controller:v1.13.3 docker push nbk8s-bo.nbartifactory.rsv.ven.veritas.com/cert-manager-webhook:v1.13.3 docker push nbk8s-bo.nbartifactory.rsv.ven.veritas.com/cert-manager-cainjector:v1.13.3
- Deploy cert-manager using the following command:
helm upgrade -i -n cert-manager cert-manager ./cert-manager-v1.13.3.tgz \
--set image.repository=nbk8s-bo.nbartifactory.rsv.ven.veritas.com/cert-manager-controller \
--set image.tag=v1.13.3 \
--set webhook.image.repository=nbk8s-bo.nbartifactory.rsv.ven.veritas.com/cert-manager-webhook \
--set webhook.image.tag=v1.13.3 \
--set cainjector.image.repository=nbk8s-bo.nbartifactory.rsv.ven.veritas.com/cert-manager-cainjector \
--set cainjector.image.tag=v1.13.3 \
--set global.imagePullSecrets[0].name=demo-secret \
--set webhook.timeoutSeconds=30 \
--set installCRDs=true \
--wait
- Run the following commands to list and verify if the cert-manager is installed:
helm list -n cert-manager
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION cert-manager cert-manager 1 <Date and Time> deployed cert-manager-v1.13.3 v1.13.3 kubectl get pods -n trust-manager
NAME READY STATUS RESTARTS AGE cert-manager-####4466d-lzgvg 1/1 Running 0 14m cert-manager-####d7754-jrd8n 1/1 Running 0 14m cert-manager-####d88bb-c79cc 1/1 Running 0 14m