Support all patch versions for a kubernetes release

[bengentil]

Hello,

This is more a question than an issue but would you be open to allow all patch versions for the supported kubernetes release
instead of a strict version comparison (eg. allowing < 1.35 instead of <= 1.34.0), maybe with a flag to activate this new behavior.

Currently the supported version is bumped on each kubernetes release which means kamaji supports 1.33.0 then 1.34.0 but in the meantime no controlplane update is possible (1.33.1 needs 1.34 to be released and supported in kamaji).

[prometherion]

@bengentil moved to Discussion section, since as you said, it's a question.

instead of a strict version comparison (eg. allowing < 1.35 instead of <= 1.34.0), maybe with a flag to activate this new behavior.

The idea of Kamaji is being a Control Plane supervisor, and it leverages the underlying Kubernetes libraries such as kubeadm and we need to understand what's the highest compatibility version it supports to prevent issues when deploying Control Planes.

I understand the patch version could be annoying since we need to wait a new release, even tho we're pretty fast: however, we could evaluate to skip patch version check, and just focus on the major and minor.

Currently the supported version is bumped on each kubernetes release which means kamaji supports 1.33.0 then 1.34.0 but in the meantime no controlplane update is possible (1.33.1 needs 1.34 to be released and supported in kamaji).

This is not true, unless we forgot to bump the KubeadmVersion constant: throughout the edge releases we bump also the k8s.io packages, and we bump that version also to support security patch releases, since they're required by our enterprise customers.