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. NetBackup™ Deployment Guide for Amazon Elastic Kubernetes Services (EKS) Cluster
  3. Troubleshooting
  4. Pod status field shows as pending
NetBackup™ Deployment Guide for Amazon Elastic Kubernetes Services (EKS) Cluster

Pod status field shows as pending

If the pod Status field shows Pending state, it indicates that Kubernetes is not able to schedule the pod. To check use the following command:

$ kubectl get all -n netbackup-operator-system

The output is something like:

NAME                     READY   STATUS    RESTARTS   AGE
pod/msdp-operator-
controller-manager-
65d8fd7c4d-bsgms           2/2     Running   0          12m

pod/netbackup-
operator-controller-
manager-6c9dc8d87f
-pq8mr                     0/2     Pending   0          15s

For more details use the following pod describe command:

$ kubectl describe pod/netbackup-operator-controller-manager-6c9dc8d87f-pq8mr -n netbackup-operator-system

The output is something like:

  Type     Reason            Age                Message
  ----     ------            ----                  -------
  Warning  FailedScheduling  56s (x3 over 2m24s)   0/4 nodes are
                                                   available:1 node(s)
                                                   had taint {node- 
                                                   role.kubernetes.
                                                   io/master: }, that
                                                   the pod didn't
                                                   tolerate, 3 node(s) 
                                                   didn't match
                                                   Pod's node
                                                   affinity/selector.

To resolve this issue verify the nodeSelector settings in the operator/patch/operator_patch.yaml file.

Feedback

Was this page helpful?
Previous

Check primary server status

Next

Ensure that the container is running the patched image

Feedback

Was this page helpful?