Request for Events Generation for Automatic Changes in Cluster State

[huaqing1994]

In the CAPI, there are certain behaviors that automatically trigger changes in the cluster state, such as certificate rotation and MHC. After these behaviors occur, we can only know what happened by querying the logs.

I would like to propose that for such automatic behaviors, corresponding events should be generated. This would allow for easier observation of these changes and enable other systems to be aware of them in a more streamlined manner.

Implementing event generation for these actions would improve overall observability and strengthen integration capabilities with other monitoring and automation systems.

Thank you for considering this enhancement.

[k8s-ci-robot]

This issue is currently awaiting triage.

If CAPI contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[chrischdi]

Did you consider to rely on metrics (e.g. via kube-state-metrics + custom config) instead (e.g. via condition metrics)?

events are not an api we provide, nor is standardized what they contain.

[fabriziopandini]

Long term I would like to have a general review of CAPI events, because even if this is not a stable API, people find them helpful.

WRT to this request, it would be great to have some more details about what Automatic Changes are not yet tracked (or are not tracked properly with events)