For the version skew policy. Why the kubectl just support minor versions N+1, N and N-1? Is there any plan to support N-2 or N-3 minor versions like kubelet?

[qing-chi-2013]

Describe the issue

Hi team,

In our production, we are using the Kubectl to drain nodes automatically. Recently, we want to support the version skew policy. It is said, that we upgrade Kubernetes master nodes only and keep the old version of worker nodes. However, according to the Kubectl policy, it just supported minor versions N+1, N, and N-1. Is there any plan to support N-2 or N-3 minor versions for Kubectl like Kubelet? Or, is there any solution to replace Kubectl?

Thanks, -qing

[YanzhaoLi]

Can anyone help look at this request? Or help provide some docs to refer to? Why does kubectl only support N-1 version against the control plane?

[YanzhaoLi]

/sig cli

[hariscats]

Compared to kubelet though, kubectl needs to maintain compatibility with a wide range of API resources and operations, which explains a stricter version skew policy.

Supporting a larger version skew would require more extensive testing to ensure compatibility across a wider range of versions, which would increase the complexity and resources needed for testing.

A server-side version of kubectl apply is something that's being considered given the last KubeCon (What's New with Kubectl and Kustomize … and How You Can Help!) session (on YouTube) and that would address the version skew issue by handling the resource application logic directly on the server. This means kubectl tool wouldn't need to be tightly synced with the server's K8s version for the apply functionality.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.