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.

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

Clarifying Version Skew Policy #1511

Closed
Sarah-A opened this issue Feb 1, 2024 · 3 comments
Closed

Clarifying Version Skew Policy #1511

Sarah-A opened this issue Feb 1, 2024 · 3 comments

Comments

@Sarah-A
Copy link
Contributor

Sarah-A commented Feb 1, 2024

We are seeking clarifications regarding C# kubernetes-client backward compatibility with older kubernetes api versions. Specifically:

  1. What is your version skew policy?
    From looking at the readme, I see that kubernetes api server support n-2 (or n-3) versions (and their matching C# clients). However, I couldn’t find any documentation regarding the opposite - does the C# kubernetes-client support older versions of the kubernetes api. For example, does C# sdk 1.13 supports AKS 1.27?
  2. If you’re not backward compatible with older AKS versions, do you backport fixes (specifically security patches) to older client versions?

Thanks!

@brendandburns
Copy link
Contributor

brendandburns commented Feb 1, 2024

Yes, this client is backward compatible in the same way as the Kubernetes version policy.

The basic way that this works is that for each new version (e.g. 12.0.x) the code is generated from the openapi/swagger document which is returned by a Kubernetes version running the corresponding version (e.g. 1.28.x).

As a result, the objects that are generated will follow the Kubernetes version policy.

In practice, this client supports much older clusters, many of the Kubernetes resources haven't changed very much (or at all) in a long time. So in practice a modern client should be able to use basic functionality in very old kubernetes versions, but it's not guaranteed.

Regarding backports, this is an open source project so generally we would expect users to contribute back-ports or cherry-picks, this is a community effort.

Hope that helps.

@Sarah-A
Copy link
Contributor Author

Sarah-A commented Feb 1, 2024

Perfect! Thanks a lot @brendandburns 🙏
I'll submit a PR to update the readme with this info.

@brendandburns
Copy link
Contributor

Closing since #1514 merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants