kubernetes version 1.30.8

[senthil13]

Based on the information available, there is no specific version of Strimzi that officially supports Kubernetes 1.30.8. The latest versions of Strimzi, including 0.45.0, noted to 1.25+ version only. That means we can deploy the 0.45.0 on k8s 1.30.8

Currently, we do have Strimizi version 0.31.1 with k8s version 1.21.12. Our Kubernets will be upgrade to 1.30.8 so we are planning what we can do the strimizi. kind of planning the upgrade plan.

Thanks
Senthil

[im-konge]

Yeah as you mentioned, we support 1.25 and above.
We are testing Strimzi on both 1.25 and the latest available version of K8s.
That means it should work fine on 1.30.8

[senthil13]

Thanks for the quick response. @im-konge

Ideally, we should upgrade to latest and greatest, but if we dont upgrade the strimzi version to 0.45.0 and stay in 0.31.1 with the latest k8s version, that will work right?

Why I am asking this is, we will move our kafka cluster to newly built k8s cluster then we can plan for upgrade the strimzi version. This way we are doing one change at a time. (first k8s version upgrade then strimzi upgrade)

Thanks
Senthil

[im-konge]

It's hard to say what will and will not work with the 0.31.1 version as it is pretty old version and a lot of things changed since the version was released - in case that you will upgrade just the K8s cluster first.

It seems that K8s 1.21 was supported in 0.39.0 as a last release (which is anyway still quite old).

I mean, if you want to see that Strimzi 0.45.0 works fine on 1.21, so you can upgrade Strimzi first and then K8s, you can do that on some test-environment.

I think that the safest thing would be to upgrade Strimzi and K8s all-together with some steps -> so you upgrade to 0.39.0 Strimzi, then you upgrade K8s to something else (for example 1.25), then again Strimzi to 0.45.0 and finally, upgrade K8s to 1.30.

Keep in mind that there can be changes needed, so it would be worth to do the upgrade path firstly somewhere outside the prod environment.

[im-konge]

I think that it should be possible to upgrade to 0.45.0 directly on the K8s 1.21, but I never tried it TBH, that's why I don't want to recommend it without checking on some test-env first.

[ppatierno]

Take into account that upgrading Strimzi first would anyway mean upgrading Kafka as well to a newer version so it's not going to be just one upgrade but at least twice. Anyway as Lukas said it's difficult to say if such an old Strimzi version works on a newer Kubernetes. You should test it first in a dev environment.

[senthil13]

Thanks for explanation,