For Kafka infrastructure managed with GitOps, a deployment pipeline turns declarative configuration in Git into cluster changes. A push triggers the pipeline, which compares the declared configuration with the current cluster state and applies only the changes needed. This contrasts with committing scripts that create resources: Git records the desired final state, enabling review, history, and rollback. section 10.2.2
A Kafka configuration pipeline can:
- Use a periodic validation pipeline to detect drift from Git and suggest corrective changes when manual edits occur. section 10.2.2
- In a Customer 360 ODS, convert AsyncAPI definitions into Kafka-compatible resources, commit generated files to Git, and synchronize the cluster. This bridges architecture and implementation without requiring Kubernetes operators. section 10.2.5
Figure 10.1 Applying Kafka cluster modifications via GitOps: after the updated Kafka cluster configuration is pushed, the CI/CD pipeline retrieves the current cluster state, calculates the required modifications, and applies them.
Shows the pipeline retrieving cluster state, calculating required modifications, and applying them after configuration changes reach Git. section 10.2.2
