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
Hi,
To gracefully update my cluster's node groups I mark old nodes as NoSchedule.
This generates alerts of type KubeDaemonSetMisScheduled, which I had to disable, but it also generates KubeDaemonSetRolloutStuck, which is should not, as my daemonsets are going great.
The text was updated successfully, but these errors were encountered:
Hi,
To gracefully update my cluster's node groups I mark old nodes as
NoSchedule
.This generates alerts of type
KubeDaemonSetMisScheduled
, which I had to disable, but it also generatesKubeDaemonSetRolloutStuck
, which is should not, as my daemonsets are going great.The text was updated successfully, but these errors were encountered: