[Bug]: kafkaNodePool migration fails when using gp3 storage class #10307
Closed
mafitconsulting
started this conversation in
General
Replies: 2 comments 3 replies
-
The migration instructions tell you to use the exactly same storage configuration in the KafkaNodePool as you have in the Kafka resource. Now your Kafka resource uses this:
While your KafkaNodePool resource uses this:
So, apart from changing the storage class, you also changed the storage type to JBOD storage. You need to do the migration with the exact same configuration. If you want to move to a different storage class or to use JBOD storage, you should first migrate to the node pools using the old storage, than create a new node pool with the new storage configuration, move all data to the new nodes and then delete the old nodes. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Bug Description
Following the documented instructions here. I am trying to migrate an existing cluster to use KafkaNodePools. The storage class which is currently used is gp3 pv. I create a kafkaNodePool manifest with following storage configuration
This configuration matches the existing storage configuration in the kafka resource
So, same storage class, same size and same type. I have the following annotations on the kafka resource
strimzi.io/node-pools: enabled
Steps to reproduce
strimzi.io/node-pools: enabled
annotationExpected behavior
Expected behaviour is for KafkaNodePools to take over the storage management of the Kafka node and not see the error message
Strimzi version
Operator 0.41 Kafka 3.7.0
Kubernetes version
1.28
Installation method
Helm Chart
Infrastructure
EKS
Configuration files and logs
[
report-05-07-2024_08-44-23.zip
](url)
Additional context
No response
Beta Was this translation helpful? Give feedback.
All reactions