As a project, we've been trying to make the core k/k repo smaller and instead push new APIs and efforts to other repos. This has been particularly noticeable with Gateway API and Network Policy API, both of which are relying on CRDs. This has been great for enabling subprojects to collaborate on new APIs, but it has also left some open questions. Particularly, what happens when these APIs reach GA? Should they be included by default in Kubernetes?
If not, how can we convince users to migrate from old APIs that are included by default in Kubernetes to new APIs that are not?
If so, how can we make this work without tightly coupling release cadences? Should we have a min-version mapping where each Kubernetes minor version needs to include a minimum of
x for the APIs released separately?
kubernetes-sigs/gateway-api#3576 includes some prior discussion on this topic. Although this discussion is starting in Gateway API, we expect it to be broadly relevant to the entire ecosystem as more APIs are developed with CRDs.
***
Got an idea for a session?
Submit your topic or upvote existing ones that catch your eye in our
GitHub Discussion. The Summit co-chairs and CNCF Projects Team will make decisions about which sessions to add to the schedule midday during the Summit, based on community votes.
