PodDisruptionBudget recreated on every cluster reconciliation
See original GitHub issueHello,
Could you please advise if it is the expected behavior that the Cluster Operator recreates the PodDisruptionBudget objects for Kafka and Zookeeper on every cluster reconciliation run? The payload of the object never changes, only metadata does.
This seems to be independent from whether I configure spec.[kafka|zookeper].template.podDisruptionBudget
or not. I have tested it with Strimzi 0.17.0, older releases may behave the same way.
Thanks Michael
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Specifying a Disruption Budget for your Application - Kubernetes
When the cluster operator contacts you, prepare for downtime, and then delete the PDB to indicate readiness for disruption. Recreate afterwards.
Read more >Configuring a cluster for pods | OpenShift Container Platform 4.9
The PodDisruptionBudget is considered healthy when there are at least minAvailable pods running in the system. Every pod above that limit can be...
Read more >Configuring Strimzi (In Development)
Instead, for each reconciliation, it checks whether a maintenance window is ... pods are recreated if needed, but no other changes happen to...
Read more >Controllers and Reconciliation - The Cluster API Book
From the kubebuilder book: Controllers are the core of Kubernetes, and of any operator. It's a controller's job to ensure that, for any...
Read more >Using RabbitMQ Cluster Kubernetes Operator - VMware Docs
Set a Pod Disruption Budget; Configure TLS; Find Your RabbitmqCluster Service Name and Admin Credentials; Use HashiCorp Vault; Verify the ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ok, thanks for clarification … I will keep it in mind. I will look at it. But migth get to it only after the upcomming 0.18.0 release.
Changing this to bug to make it cleaer that this is not just a question.