Open fabriziopandini opened 2 months ago
This issue is currently awaiting triage.
CAPI contributors will take a look as soon as possible, apply one of the triage/*
labels and provide further guidance.
I guess we can already work on deprecating the current Available condition and adding the new one? (then we only have to drop the old one with the next apiVersion, otherwise we then have to wait another apiVersion)
(just mentioning this because we were often ~ interpreting "api-change" as "this has to wait until we cut the new apiversion" in a lot of cases, and it's not true, we actually have to do something before)
I guess we can already work on deprecating the current Available condition and adding the new one?
That's correct
What would you like to be added (User Story)?
As a user I would like clear observability signals.
Detailed Description
As per https://github.com/kubernetes-sigs/cluster-api/issues/3779 discussion:
This issue is about the last point. My preference goes to introduce a KCP.Initialized condition (that mirrors ControlPlane.status.initialized)
Anything else you would like to add?
No response
Label(s) to be applied
/kind cleanup /kind api-change /area control-plane /priority important-longterm