Amend Compatibility table to document n-2 version guarantees.#1184
Conversation
|
Welcome @Capstan! |
|
/assign @brendandburns |
yue9944882
left a comment
There was a problem hiding this comment.
i believe you're referring to this page where it says:
The Kubernetes project maintains release branches for the most recent three minor releases (1.18, 1.17, 1.16).
/lgtm
|
The clients should really continue to work for longer than that. It's really feature deprecation that happens. Our existing go client libraries mix in stuff that doesn't stop being correct (machinery) with stuff that does change over time (the api types), which is unfortunate. |
| Kubernetes cluster, but everything they have in common will work. | ||
| * `-` The Kubernetes cluster has features the java-client library can't use | ||
| (additional API objects, etc). | ||
| * `x` The Kubernetes cluster has no guarantees to support the API client of |
There was a problem hiding this comment.
Can we change this to "is not tested" rather than "may simply break"
There was a problem hiding this comment.
IIUC, it's more than just "not tested". If an API version is deprecated, and two versions later it is removed, then that functionality will simply not work.
There was a problem hiding this comment.
Tried to keep clarity while softening the statement. PTAL.
|
I'm not necessarily opposed to this, but our APIs have really rarely changed, I'd like the language to be a little weaker so that we don't scare people away. |
|
@Capstan friendly ping, thanks! |
770632f to
3ba603c
Compare
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: brendandburns, Capstan The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Thanks! |
I don't have a link at the moment, but IIRC, kubernetes masters only promise backwards compatibility of two versions of the API client, so running a version older than that may run into potholes of broken behavior as the master no longer supports a deprecated/removed API.
/cc @lavalamp