Please enter search query.
Search <book_title>...
NetBackup™ Deployment Guide for Kubernetes Clusters
Last Published:
2023-04-24
Product(s):
NetBackup (10.2)
- Introduction
- Section I. Deployment
- Prerequisites for Kubernetes cluster configuration
- Deployment with environment operators
- Deploying NetBackup
- Primary and media server CR
- Deploying NetBackup using Helm charts
- Deploying MSDP Scaleout
- Deploying Snapshot Manager
- Section II. Monitoring and Management
- Monitoring NetBackup
- Monitoring MSDP Scaleout
- Monitoring Snapshot Manager
- Managing the Load Balancer service
- Managing MSDP Scaleout
- Performing catalog backup and recovery
- Section III. Maintenance
- MSDP Scaleout Maintenance
- Upgrading
- Uninstalling
- Troubleshooting
- Troubleshooting AKS and EKS issues
- Troubleshooting AKS-specific issues
- Troubleshooting EKS-specific issues
- Troubleshooting AKS and EKS issues
- Appendix A. CR template
Resolve an issue related to pulling an image from the container registry
Primary or media server failed to deploy with
error. If the pod Status field displays , it means that the pod could not start because Kubernetes cannot pull a container image. A misspelled registry or image name or image registry being not reachable can cause a status.Run the $ k get all -n netbackup-operator-system command.
The output should look like:
NAME READY STATUS RESTARTS AGE pod/msdp-operator -controller-manager- 65d8fd7c4d-bsgms 2/2 Running 0 7m9s pod/netbackup-operator -controller-manager- 5df6f58b9b-6ftt9 1/2 ImagePullBackOff 0 13s
For additional details, use the following command:
$ kubectl describe pod/<pod_name> -n netbackup-operator-system
Resolve this issue using any of the following methods:
Check if image name and tag are correct. If not, edit and update the environment CR using the kubectl edit environment <environment CR-name> -n <namespace> command with correct image name and tag, and then save the changes.
Check if the user is authorized and has permissions to access the Azure/AWS container registry.