Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Call handlers for cluster events #20

Closed
kopf-archiver bot opened this issue Aug 18, 2020 · 1 comment
Closed

Call handlers for cluster events #20

kopf-archiver bot opened this issue Aug 18, 2020 · 1 comment
Labels
archive enhancement New feature or request

Comments

@kopf-archiver
Copy link

kopf-archiver bot commented Aug 18, 2020

An issue by nolar at 2019-04-02 09:49:57+00:00
Original URL: zalando-incubator/kopf#20
 

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

@kopf-archiver kopf-archiver bot closed this as completed Aug 18, 2020
@kopf-archiver kopf-archiver bot changed the title [archival placeholder] Call handlers for cluster events Aug 19, 2020
@kopf-archiver kopf-archiver bot added the enhancement New feature or request label Aug 19, 2020
@kopf-archiver kopf-archiver bot reopened this Aug 19, 2020
@nolar
Copy link
Owner

nolar commented Apr 4, 2021

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.

@nolar nolar closed this as completed Apr 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
archive enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant