Replies: 1 comment
|
Pod Disruption Budgets for the operands are always enabled by default. For the Operator you have to enable it yourself IIRC. So maybe you are mixing the two things together? As for the PDBs for the operands, you can disable their management completely through and environment variable in the Cluster Operator and manage them yourself. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I'm using the Helm deployment of the cluster operator. The operator is deployed to a separate namespace called
kafka-system. I want the the operator to manage different namespaces in my Kubernetes so I havewatchAnyNamespace=true. According to the docs, by defaultpodDisruptionBudgetis not turned on, but after the Kafka cluster is created I see a PDB created in my target namespace. For example I have a 5-node Kafka created by the operator, it creates a PDB requiring min available of 4.The docs mention a value that can be set for
podDisruptionBudget.enabled, which defaults tofalse, so I'm unsure as to why my Kafka is being created with this PDB. Moreover, playing with the override by settingpodDisruptionBudget.enabledtotrue, it actually creates a PDB in the namespacekafka-systemwhere the operator is deployed instead which makes me more confused as to what it'd be for?My question is, is there a way to disable the PDB creation for the Kafka cluster itself, or manipulate the value it's set as?
All reactions