Add PodDisruptionBudget for csi-provisioner controller#1695
Open
huww98 wants to merge 1 commit into
Open
Conversation
Ensures at least one controller pod remains available during voluntary disruptions (e.g. node drain), preventing provisioning downtime.
k8s-ci-robot
added
kind/feature
Contributor
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: huww98 The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
k8s-ci-robot
added
the
approved
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
/kind feature
What this PR does / why we need it:
Adds a PodDisruptionBudget for the csi-provisioner Deployment with
maxUnavailable: 1. This ensures at least one controller pod remains available during voluntary disruptions (e.g. node drain), preventing provisioning downtime.Enabled by default, configurable via
controller.pdb.enabledandcontroller.pdb.maxUnavailablein values.yaml.Which issue(s) this PR fixes:
NONE
Special notes for your reviewer:
Reference: AWS EBS CSI driver has a similar PDB enabled by default for their controller.
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: