kubernetes-sigs/cluster-api

Request for Events Generation for Automatic Changes in Cluster State

Open

#11,944 opened on Mar 10, 2025

View on GitHub
 (10 comments) (0 reactions) (1 assignee)Go (1,532 forks)auto 404
help wantedkind/featurepriority/backlogtriage/accepted

Repository metrics

Stars
 (4,267 stars)
PR merge metrics
 (PR metrics pending)

Description

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.

Contributor guide

Research direction
Examine existing event generation in Cluster API, particularly for actions like certificate rotation and MHC. Implement similar event creation using the Kubernetes event recorder.
Tech stack
go
Domain
backendapidevops
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoKubernetesCluster API
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40