Skipping patch versions ?

[olevitt]

What happened?

Documentation (https://github.com/kubernetes-sigs/kubespray/blob/master/docs/upgrades.md) links to this reply : #3849 (comment) that states that skipping versions is not supported.
Does this also apply to patches releases ? e.g 2.23.2 was just released and 2.24.0 is set to be released in 2 days. Could someone on 2.23.1 (or 2.23.0) skip the 2.23.2 and upgrade directly to 2.24.0 ?

What did you expect to happen?

N/A

How can we reproduce it (as minimally and precisely as possible)?

N/A

OS

N/A

Version of Ansible

2.23.1

Version of Python

N/A

Version of Kubespray (commit)

N/A

Network plugin used

calico

Full inventory with variables

No response

Command used to invoke ansible

No response

Output of ansible run

No response

Anything else we need to know

No response

[VannTen]

The same documentation mentions going to 2.6.0 to 2.7.0, so that points to skipping patch releases as supported.
I guess that could use a more explicit mention

[VannTen]

@yankay @floryut I think it should works right now, but that's probably worth making it explicit and if upgrades between 2.N.X and 2.(N+1).Y does not work, that should be a bug.
wdyt ?

[yankay]

@yankay @floryut I think it should works right now, but that's probably worth making it explicit and if upgrades between 2.N.X and 2.(N+1).Y does not work, that should be a bug. wdyt ?

HI @VannTen

Yes, I think it's a design goal. However, there is a lack of automatic CI to test it.