This is a Feature Request
What would you like to be added
Kubernetes maintains a canonical stable-<major>.<minor>.txt marker for every supported minor release (until EOL), which resolves to the latest patched version for that minor-- e.g. stable-1.34.txt returns v1.34.9. For example:
% curl -L -s https://dl.k8s.io/release/stable-1.34.txt
v1.34.9%
This adds an example showing how to substitute stable-<major>.<minor>.txt
for stable.txt to download the latest patched kubectl for any supported older minor version.
Why is this needed
The existing docs only show downloading stable.txt (the current latest release). Users who need an older minor — for example, to stay within the version skew policy against an older control plane — have no documented way to get the latest patch of that minor, and are left guessing a specific patch version by hand.
Many sites are on slightly older versions of k8s, and this will help them to at least get the latest version of the CLI.
This is a Feature Request
What would you like to be added
Kubernetes maintains a canonical
stable-<major>.<minor>.txtmarker for every supported minor release (until EOL), which resolves to the latest patched version for that minor-- e.g.stable-1.34.txtreturnsv1.34.9. For example:This adds an example showing how to substitute
stable-<major>.<minor>.txtfor
stable.txtto download the latest patched kubectl for any supported older minor version.Why is this needed
The existing docs only show downloading
stable.txt(the current latest release). Users who need an older minor — for example, to stay within the version skew policy against an older control plane — have no documented way to get the latest patch of that minor, and are left guessing a specific patch version by hand.Many sites are on slightly older versions of k8s, and this will help them to at least get the latest version of the CLI.