# Quick Command Reference for ZooKeeper to KRaft Migration This topic provides quick access to frequently used commands during migration. Commands are organized by migration phase for easy reference. ## Verify pre-migration requirements ```bash # Check Confluent for Kubernetes (CFK) version kubectl get deployment confluent-operator -n \ -o jsonpath='{.spec.template.spec.containers[0].image}' # Check Confluent Platform version kubectl get kafka -n \ -o jsonpath='{.spec.image.application}' # Check current inter-broker protocol version kubectl exec -n -- \ grep "inter.broker.protocol.version" \ /opt/confluentinc/etc/kafka/kafka.properties # Verify Kafka pods are running kubectl get pods -n -l app=kafka # Verify ZooKeeper is healthy kubectl get pods -n -l app=zookeeper # Check for existing KRaftController kubectl get kraftcontroller -n # Expected: No resources found # If RBAC is enabled, verify MDS endpoint kubectl exec -n -- curl -k -s -o /dev/null \ -w "HTTP %{http_code}\n" \ https://:8090/security/1.0/authenticate # Expected: HTTP 401 ``` ## Monitor migration progress ```bash # Check migration phase kubectl get kraftmigrationjob -n \ -o jsonpath='{.status.phase}' # Check migration subphase kubectl get kraftmigrationjob -n \ -o jsonpath='{.status.subPhase}' # Watch migration progress in real time watch -n 5 'kubectl get kraftmigrationjob -n \ -o jsonpath="{.status.phase} - {.status.subPhase}"' # Check CFK Operator logs for migration status kubectl logs deployment/confluent-operator -n --tail=20 | \ grep "Migration current status" # Monitor pod status during rolls watch kubectl get pods -n ``` ## Validate DUAL-WRITE phase ```bash # Verify DUAL-WRITE mode (Method 1 - most reliable) kubectl get kraftmigrationjob -n \ -o jsonpath='{.status.phase}' # Expected: DUAL-WRITE # Verify DUAL-WRITE mode (Method 2 - via Jolokia) kubectl exec -n -- curl -s \ http://localhost:7777/jolokia/read/kafka.controller:type=KafkaController,name=ZkMigrationState \ | jq '.value.Value' # Expected: 1 (DUAL_WRITE state) # Check Kafka broker status kubectl get kafka -n -o jsonpath='{.status.phase}' # Expected: RUNNING # Check KRaftController status kubectl get kraftcontroller -n \ -o jsonpath='{.status.phase}' # Expected: RUNNING ``` ## Finalization commands ```bash # Finalize migration (point of no return) kubectl annotate kraftmigrationjob \ platform.confluent.io/kraft-migration-trigger-finalize-to-kraft=true \ -n # Monitor finalization progress kubectl get kraftmigrationjob -n -w ``` ## Post-migration tasks ```bash # Release migration locks kubectl annotate kraftmigrationjob \ platform.confluent.io/kraft-migration-release-cr-lock=true \ -n # Verify locks are released kubectl get kafka -n -o yaml | \ grep kraft-migration-cr-lock # Should return nothing # Download updated Kafka CR kubectl get kafka -n -o yaml > kafka-kraft-mode.yaml # Download KRaftController CR kubectl get kraftcontroller -n -o yaml > kraftcontroller.yaml # Verify Kafka uses KRaftController (not ZooKeeper) kubectl get kafka -n \ -o jsonpath='{.spec.dependencies.kRaftController.clusterRef.name}' ``` ## Troubleshooting commands ```bash # Check for errors in CFK Operator logs kubectl logs deployment/confluent-operator -n --tail=50 | \ grep -i error # Check Kafka pod logs for errors kubectl logs -n --tail=50 | \ grep -E "ERROR|FATAL" # Check KRaftController logs for errors kubectl logs -n --tail=50 | \ grep -E "ERROR|FATAL" # Get full migration job status kubectl get kraftmigrationjob -n -o yaml # Check pod events kubectl describe pod -n ``` ## Rollback commands #### NOTE Rollback is supported during the `SETUP`, `MIGRATE`, and `DUAL-WRITE` phases. For complete instructions, see [Roll Back to ZooKeeper](co-migrate-kraft-rollback.md#co-migrate-kraft-rollback-v2). ```bash # Trigger rollback to ZooKeeper kubectl annotate kraftmigrationjob \ platform.confluent.io/kraft-migration-trigger-rollback-to-zk=true \ --overwrite -n # Delete controller node from ZooKeeper (exec into Kafka pod first) kubectl exec -it -n -- bash zookeeper-shell \ -zk-tls-config-file /opt/confluentinc/etc/kafka/zookeeper-client.properties \ deleteall /-/controller # Delete migration node from ZooKeeper zookeeper-shell \ -zk-tls-config-file /opt/confluentinc/etc/kafka/zookeeper-client.properties \ deleteall /-/migration # Continue rollback after node removal kubectl annotate kraftmigrationjob \ platform.confluent.io/continue-kraft-migration-post-zk-node-removal=true \ --overwrite -n ``` ## KRaft Migration Plugin Commands The KRaft migration plugin is available in CFK 3.2.2 and later. For installation instructions, see [Install the Confluent kubectl plugin](https://docs.confluent.io/operator/3.2/co-deploy-cfk.html#install-confluent-plugin-using-krew). | Action | Plugin Command | |----------------------------------|------------------------------------------------------------------------------------------| | List migration jobs | `kubectl confluent cluster kraft-migration list -n ` | | Check migration status | `kubectl confluent cluster kraft-migration status --name -n ` | | Finalize migration | `kubectl confluent cluster kraft-migration finalize --name -n ` | | Rollback to ZooKeeper | `kubectl confluent cluster kraft-migration rollback --name -n ` | | Remove ZK znodes during rollback | `kubectl confluent cluster kraft-migration zk-node-removal --name -n ` | | Release CR locks | `kubectl confluent cluster kraft-migration release-lock --name -n ` | For the complete plugin command reference, see [kubectl Plugin for Confluent for Kubernetes Reference](co-plugin-cli-index.md#co-plugin-cli-index). ## Related content * For the complete migration guide, see [Migrate a Single Cluster from ZooKeeper to KRaft](co-migrate-kraft-procedure.md#co-migrate-kraft-procedure-v2). * To understand what happens in each migration phase, see [ZooKeeper to KRaft Migration Phases and Sub-phases](co-migrate-kraft-phases.md#co-migrate-kraft-phases-v2).