Replies: 1 comment 6 replies
-
Well, you can try to change the version number to some supported version in the Kafka CR and see if it helps. I'm not sure what changes were between 0.19 and 0.20 anymore ... it might upgrade smoothly, but if it does not, just delete the Kafka pods / stateful set (without the persistent volumes) and the operator should recover it. In 0.22 we did some changes and this should be much easier if you would want to upgrade directly to 0.22 (but there is a CRD upgrade between 0.22 and 0.23, so it would be better to not go directly from 0.19 to 0.23, but first to 0.22 if you decide to go this way). |
Beta Was this translation helpful? Give feedback.
6 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I've got a problem with upgrading operator from 0.19.0->0.20.1
Message: Unsupported Kafka.spec.kafka.version: 2.4.1. Supported versions are: [2.5.1, 2.6.0, 2.5.0]
Reason: KafkaUpgradeException
0.20.1 drops supports 2.4.1, unfortunately I've not upgraded it till supported versions.
I can't downgrade strimzi-operator due to helm2/3 bug with crd.
Is any way to upgrade kafka cluster?
Beta Was this translation helpful? Give feedback.
All reactions