Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs(node pools): reversing the migration to node pools #9950

Merged
merged 2 commits into from
Apr 12, 2024
Merged

docs(node pools): reversing the migration to node pools #9950

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
92a66fa
docs(node pools): reversing the migration to node pools
PaulRMellor Apr 11, 2024
7b533e9
docs(review): edits to doc from comments by PP
PaulRMellor Apr 12, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion documentation/modules/configuring/proc-migrating-clusters-node-pools.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ spec:
deleteClaim: false
----
+
WARNING: To migrate a cluster while preserving its data along with the names of its nodes and resources, the node pool name must be `kafka`, and the `strimzi.io/cluster` label must use the name of the Kafka resource.
WARNING: To preserve cluster data and the names of its nodes and resources, the node pool name must be `kafka`, and the `strimzi.io/cluster` label matches the Kafka resource name.
Otherwise, nodes and resources are created with new names, including the persistent volume storage used by the nodes.
Consequently, your previous data may not be available.

Expand Down Expand Up @@ -93,3 +93,12 @@ The resources remain identical to how they were before.

. Remove the replicated properties from the `Kafka` custom resource.
When the `KafkaNodePool` resource is in use, you can remove the properties that you copied to the `KafkaNodePool` resource, such as the `.spec.kafka.replicas` and `.spec.kafka.storage` properties.

.Reversing the migration

To revert to managing Kafka nodes using only `Kafka` custom resources:

. If you have multiple node pools, consolidate them into a single `KafkaNodePool` named `kafka` with node IDs from 0 to N (where N is the number of replicas).
. Ensure that the `.spec.kafka` configuration in the `Kafka` resource matches the `KafkaNodePool` configuration, including storage, resources, and replicas.
. Disable support for node pools in the `Kafka` resource using the `strimzi.io/node-pools: disabled` annotation.
. Delete the Kafka node pool named `kafka`.
Loading