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
There is no direct way of detecting the cluster events of this kind (upgrades, reboots, etc). This can only be done by indirect observations with frequent polling or watching — e.g., appearance of kind: Node with a newer version in status.nodeInfo.kubeletVersion. If needed, this can be implemented as a separate handler — there is no need to add this as the framework's feature.
Expected Behavior
Some handlers should be called when the cluster events happen, such as the cluster upgrades.
Actual Behavior
Only the objects changes cause the handlers execution.
The objects are not always changed when something else (unmonitored) happens in the cluster or with the cluster.
See also #19
The text was updated successfully, but these errors were encountered: