-
Story
-
Resolution: Done
-
Major
-
None
-
None
-
Product / Portfolio Work
-
False
-
-
False
-
2
-
None
-
None
-
CLOUD Sprint 268, CLOUD Sprint 269
Background
https://github.com/kubernetes-sigs/cluster-api/issues/10130 describes a scenario in which all controllers in Cluster API report their paused status via conditions.
This condition will be used as part of the handover mechanism between Machine API and Cluster API versions of resources.
Steps
- Now the upstream CAPI controllers have the paused condition, we need to ensure the providers are also setting it appropriately
- Identify the controllers in CAPA that need the paused condition set to conform to the new contract.
Stakeholders
- Cluster Infra
- Upstream CAPI
Definition of Done
- Upstream CAPA resources report paused via a condition that acknowledges that they have been paused.
- Docs
- <Add docs requirements for this card>
- Testing
- <Explain testing that will be added>
- clones
-
OCPCLOUD-2562 Implement consistent reporting of paused resources in Cluster API
-
- Closed
-
- depends on
-
OCPCLOUD-2855 Rebase/update to K8s 1.31 for Cluster API Provider AWS
-
- Closed
-