-
Notifications
You must be signed in to change notification settings - Fork 15
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
feat(dp): handle PodDisruptionBudget reconciliation for deployment #464
Conversation
fae1cd7
to
1278780
Compare
d19eae8
to
93cc2e4
Compare
The E2E are failing due to policy rules not being in place in the helm chart (a sad reality of chicken and egg problem in tests :/)
I'm not sure if we want to solve it differently than adding rules from this PR to helm chart already. We could be tempted to patch the policy rules in tests but that can be error prone. I'm curious to your thoughts on this. |
Yeah, I agree that's better to add the rules already to the helm chart. At least by having these E2Es failing, it gives us direct feedback on the missing pieces and we're fixing them in the right place. By patching them, we'd still have to remember to add the rules to the chart eventually. Adding them and releasing straight away: Kong/charts#1114 |
Co-authored-by: Patryk Małek <patryk.malek@konghq.com>
What this PR does / why we need it:
Adds PodDisruptionBudget reconciliation for DataPlanes.
Which issue this PR fixes
Fixes #142.
PR Readiness Checklist:
Complete these before marking the PR as
ready to review
:CHANGELOG.md
release notes have been updated to reflect significant changes