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
As per the message in confirmation box, the pods in the namespace are scaled down to zero; but I see all pods are running in the kube-system namespace even after I put the space to sleep
Confirmation Box
data on UI and status of pods are not matching
The text was updated successfully, but these errors were encountered:
@mahendrabagul thanks for creating this issue! I guess the kube system namespace is a little bit special here as those pods do not have a replica set or statefulset as owner. In general its not a good idea as well to let kube system sleeping as it would kill the cluster essentially completely, so this is more or less working as intended
@FabianKramm Yeah agree. However, can we show the same on the UI by some mean? This will just let use know that the kube-system namespace cant be put to sleep. :D
As per the message in confirmation box, the pods in the namespace are scaled down to zero; but I see all pods are running in the kube-system namespace even after I put the space to sleep
Confirmation Box
data on UI and status of pods are not matching
The text was updated successfully, but these errors were encountered: