[Feature] Deploy/maintain the correct PodDisruptionBudget
configuration according to the Etcd resource status conditions
#165
Labels
kind/enhancement
Enhancement, improvement, extension
lifecycle/stale
Nobody worked on this for 6 months (will further age)
release/beta
Planned for Beta release of the Feature
Milestone
Feature (What you would like to be added):
Deploy/maintain the correct
PodDisruptionBudget
configuration according to theEtcd
resource status conditions.Motivation (Why is this needed?):
Pick individually executable pieces of the multi-node proposal.
Approach/Hint to the implement solution (optional):
The deployment of
PodDisruptionBudget
resource is probably best done in the main controller and the dynamic modification of the resource based on theEtcd
resourcestatus
is best done in the custodian controller.It is probably better to deploy the
PodDisruptionBudget
only for the multi-node case (spec.replicas > 1
) because deploying it for the single-node case might block node drain.The text was updated successfully, but these errors were encountered: