Hello, I have a question regarding the deployment of Kafka using Kraft controllers in a Kubernetes environment. Our current Kafka cluster is deployed on K8S clusters as statefulsets without operators and our brokers are configured to use a script which marks the containers as unready if under-replicated partitions exist. With this readiness check and a pod disruption budget of the minimum in sync replica - 1, we are able to perform rollout restarts of our brokers automatically without ever producing consumers and producers errors.
We have started the processes of transitioning to Kraft and based on the recommended deployment strategy we are going to define dedicated nodes as controllers instead of using combined servers. However, defining nodes as controller does not seem to allow to use the same strategy for readiness check as the kafka-topics.sh does not appear to be executable on controller brokers. The question is: what is a reliable readiness check that can be used for Kraft controllers that ensures that rollout restart can be performed safely? Thanks, Frank -- Francesco Burato | Software Development Engineer | Adobe | bur...@adobe.com<mailto:bur...@adobe.com>
