Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Document compatibility versions #48171

Open
sftim opened this issue Oct 3, 2024 · 2 comments · May be fixed by #48207
Open

Document compatibility versions #48171

sftim opened this issue Oct 3, 2024 · 2 comments · May be fixed by #48207
Assignees
@abhilasha2418
Labels
kind/feature Categorizes issue or PR as related to a new feature. language/en Issues or PRs related to English language priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@sftim
Copy link
Contributor

sftim commented Oct 3, 2024 •
edited
Loading

This is a Feature Request

What would you like to be added
We're enhancing Kubernetes to be able to run in a mode that is compatible with older releases. For example, if you have a Helm chart that says it only works with Kubernetes v1.31, you might be able to use Kubernetes v1.33 emulating v1.31

Document this.

Why is this needed

https://kubernetes.io/releases/ mentions support for versions. Now there are two versions to consider: the version label on the release, and the range of releases that can pretend to be an older version for strict API compatibility.

If you are running v1.33, you might want to refer to the v1.31 docs for some details because that happens to be the version you happen to be emulating.
If we don't document this detail clearly, including the limitations, we risk confusing users.

Comments
/sig architecture
/sig api-machinery
/kind feature
/language en
/priority important-longterm
/triage accepted
@sftim sftim added the kind/feature Categorizes issue or PR as related to a new feature. label Oct 3, 2024
@k8s-ci-robot k8s-ci-robot added sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. language/en Issues or PRs related to English language priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on. labels Oct 3, 2024
This was referenced Oct 3, 2024
Open
Open
@sftim
Copy link
Contributor Author

sftim commented Oct 3, 2024

Prompted by kubernetes/kubernetes#127784

@abhilasha2418
Copy link
Contributor

/assign

@abhilasha2418 abhilasha2418 linked a pull request Oct 5, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@abhilasha2418 abhilasha2418

Labels
kind/feature Categorizes issue or PR as related to a new feature. language/en Issues or PRs related to English language priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Document compatibility versions abhilasha2418/website
3 participants
@k8s-ci-robot @sftim @abhilasha2418