23.2. Deploying the Streams for Apache Kafka Drain Cleaner using installation files

Procedure

1. If you are using the legacy mode activated by setting the STRIMZI_DENY_EVICTION environment variable to false, you must also configure the PodDisruptionBudget resource. Set maxUnavailable to 0 (zero) in the Kafka and ZooKeeper sections of the Kafka resource using template settings.

   Specifying a pod disruption budget

   apiVersion: kafka.strimzi.io/v1beta2
   kind: Kafka
   metadata:
     name: my-cluster
     namespace: myproject
   spec:
     kafka:
       template:
         podDisruptionBudget:
           maxUnavailable: 0
   
     # ...
     zookeeper:
       template:
         podDisruptionBudget:
           maxUnavailable: 0
     # ...

   This setting prevents the automatic eviction of pods in case of planned disruptions, leaving the Streams for Apache Kafka Drain Cleaner and Cluster Operator to roll the pods on different worker nodes.

   Add the same configuration for ZooKeeper if you want to use Streams for Apache Kafka Drain Cleaner to drain ZooKeeper nodes.

2. Update the Kafka resource:

   oc apply -f <kafka_configuration_file>

3. Deploy the Streams for Apache Kafka Drain Cleaner.

   • To run the Drain Cleaner on OpenShift, apply the resources in the /install/drain-cleaner/openshift directory.

     oc apply -f ./install/drain-cleaner/openshift