Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[K8S004] Ensure podDisruptionBudget set & at least one of minAvailable or maxUnavailable is provided #5

Open
bryantbiggs opened this issue Feb 6, 2023 · 1 comment
Labels
check feature-request Request for a new feature

Comments

@bryantbiggs
Copy link
Member

Use case

To ensure services are configured for high-availability to reduce the chance of disruption or downtime during an upgrade, users should have podDisruptionBudget set and at least one of minAvailable or maxUnavailable is provided for each workload construct (Deployment, ReplicaSet, ReplicationController, StatefulSet)

Solution/User Experience

Report on any workload constructs that do not have an associated podDisruptionBudget or if the associated podDisruptionBudget does not have minAvailable or maxUnavailable configured

Alternative solutions

None
@bryantbiggs bryantbiggs added feature-request Request for a new feature check labels Feb 6, 2023
@bryantbiggs bryantbiggs moved this to Todo in eksup Feb 14, 2023
@bryantbiggs
Copy link
Member Author

this requires the match selector helper which the go client has but the rust client currently does not

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
check feature-request Request for a new feature
Projects
Status: Todo
Development

No branches or pull requests

1 participant