-
Spike
-
Resolution: Unresolved
-
Critical
-
None
-
None
-
None
-
False
-
-
False
-
None
-
5
-
None
-
CLOUD Ready for Development, CLOUD Sprint 230
Before shudown, a bug (https://github.com/kubernetes/kubernetes/pull/114585) was found in the Kubernetes API that prevented users, in K8s 1.26 from generating valid CRDs. There are a bunch of other types that are also incompatible.
To prevent issues like this, we need to enumerate other places within the K8s API where this is an issue and from there, identify what would happen were we to make a change to the existing APIs.
The idea is to create a document enumerating the problem areas, and then try to work out what the effect is to the data should we make a change to the APIs.
Once completed, this will be presented to the sig-api-machinery meeting for further discussion.
DoD:
- Document describing the existing issues and potential changes in breaking the API
- Present topic at sig-api-machinery
- Attach recording here
Upstream slack conversation: https://kubernetes.slack.com/archives/C0EG7JC6T/p1671469132445819