kubernetes
Create a list of all patch releases
What would you like to be added:
I would like there to be an easily available list with all released versions of kubectl.
Why is this needed:
With kubectl, unlike many other programs, it is often not a good idea to run the latest available version. One should instead use the version number that matches the Kubernetes cluster you are currently working towards. But while I need to stay within the version skew, I do want to use the latest patch release (in case something important has been fixed). So what I'm frequently looking for is "kubectl v1.26.x" where x is the latest patch release for kubectl v1.26. But in my experience, it is hard to find x.
There are instructions for installing a specific kubectl version in the Kubernetes documentation, but there is no reference on how to find the latest patch release of a given kubectl minor version.
So I went to this repo, expecting to find GitHub Releases where I can easily filter on the version number. But that's apparently not used by this repo, instead there are tags. Using tags in Git can be very helpful for development, but they are not very informative for the end user. For example are there both kubernetes-1.28.2 and 0.28.2 and I don't know what they refer to. Using 0.28.2 sounds very old, so I assume that's not the kubectl version?
So I would like there to be an official list of all the kubectl releases. Preferably with the relevant release notes attached. This could take the form of using GitHub Releases, but a simple txt file published in a reasonable place would be good enough for my use case. Or, at the very least, it would be helpful with some documentation explaining what the different tags stand for.
This issue is currently awaiting triage.
SIG CLI takes a lead on issue triage for this repo, but any Kubernetes member can accept issues by applying the triage/accepted label.
The triage/accepted label can be added by org members by writing /triage accepted in a comment.
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/test-infra repository.
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/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas 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
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/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas 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