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
Resolving an issue related to invalid nodepool
Invalid nodepool is mentioned in primary server or media server CR nodeSelector spec. Due to this, primary server or media server pod fails to schedule.
The following error is displayed:
Error: Did not match Pod's node affinity/selector.
To resolve an issue related to invalid nodepool
- If you are deploying NetBackup on Kubernetes Cluster for the first time, delete the respective CR.
If it is primary server CR:
Delete it using the kubectl delete -f <environment.yaml> command.
Update the node selector in primary server section in
environment.yaml
and apply it again using the kubectl apply -f <environment.yaml> command.
- For media server CR: Delete the media server CR by removing the mediaServer section in the
environment.yaml
and save the changes.Note:
Ensure that you copy spec information of the media server CR. The spec information is used to reapply the media server CR.
- Apply the new changes using the kubectl apply -f <environment.yaml> command.
- Add the mediaServer section, update the nodeSelector, and reapply the
environment.yaml
using the kubectl apply -f <environment.yaml> command.