説明
This is a Feature Request
What would you like to be added
Add information to the version skew policy doc detailing which versions of Kubernetes API server work with which versions of Etcd.
Why is this needed
With the introduction of etcd 3.6, supported by Kubernetes 1.34, it has once again become an issue that we do not have a document anywhere that shows possible and required upgrades for etcd based on your upgrades of Kubernetes. Whenever we release etcd 3.7 this will become even more necessary.
Comments
This documentation task should be suitable for a new Docs contributor who has some time to talk to SIG members.
The completed document would likely be a chart, showing which supported versions of Kubernetes match up with which supported minor versions of etcd (e.g. v3.5, v3.6). We would limit this to non-EOL versions just to limit scope/size.
It would also include some narrative about upgrading etcd, linking to the official etcd upgrade documentation.
Steps to fulfill this would include:
- Talk to SIG-Etcd and SIG-API-Machinery to confirm Kubernetes::Etcd version correspondance
- Prepare a version skew chart and get approval by both sigs.
- Draft a new section in the Version Skew doc that contains the required information above.
I am available to advise a new contributor on writing this doc; comment below or find jberkus in #sig-etcd slack channel.
This has previously been created as an issue and not implemented, but was never documented in a way that would allow a new contributor to pick it up.
/sig etcd /sig api-machinery /help