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 Amazon Elastic Kubernetes Service 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.yamland 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.yamland 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.yamlusing the kubectl apply -f <environment.yaml> command.