Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. Cohesity Cloud Scale Technology Manual Deployment Guide for Kubernetes Clusters
  3. Section IV. Maintenance
  4. Troubleshooting
  5. Troubleshooting AKS and EKS issues
  6. Resolving an issue related to invalid nodepool
Cohesity Cloud Scale Technology Manual Deployment Guide for Kubernetes Clusters

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

  1. For media server CR, ensure that you copy spec information of the media server CR. The spec information is used to reapply the media server CR.
  2. Edit the environment CR using the following command in primary/mediaServer section in environment CR update the nodeSelector, and save the changes

    helm upgrade cloudscale cloudscale-<version>.tgz -n netbackup --reuse-values --set environment.primary.nodeSelector.labelKey=agentpool --set environment.primary.nodeSelector.labelValue=nbupoo

Feedback

Was this page helpful?
Previous

Resolving an issue related to insufficient storage

Next

Resolve an issue related to KMS database

Feedback

Was this page helpful?