You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is not perfect since it actually loads all replicasets and then filter them using unreliable way. Also the command won't show the situation when DESIRED = 2 but RUNNING = 1. I would like to get all ReplicaSets that have any problems using kubectl only without external monitoring systems.
Is this possible and how to do that?
Thank you.
UP: actually, the same question is actual for deployments and daemonsets (pseudo-output):
kubectl get deployment
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
blablah 2 1 1 1 35d
kubectl get daemonsets -n kube-system
NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
kube-proxy 11 11 10 11 10 <none> 179d
The text was updated successfully, but these errors were encountered:
Right now I'm using the trick to find all replicasets that have DESIRED bigger than 0 but zero CURRENT or READY pods:
This is not perfect since it actually loads all replicasets and then filter them using unreliable way. Also the command won't show the situation when DESIRED = 2 but RUNNING = 1. I would like to get all ReplicaSets that have any problems using kubectl only without external monitoring systems.
Is this possible and how to do that?
Thank you.
UP: actually, the same question is actual for deployments and daemonsets (pseudo-output):
The text was updated successfully, but these errors were encountered: