chore: Add PDB for distributors #16487
Open
+8
−0
Conversation
This file contains 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
poyzannur
force-pushed
the
poyzan/add-pdb-for-distributors
branch
from
e387008 to
8639b8f
Compare
poyzannur
changed the title
poyzannur
changed the title
| @@ -47,6 +47,14 @@ local k = import 'ksonnet-util/kausal.libsonnet'; | |||
| else | |||
| k.util.antiAffinity, | |||
|
|
|||
| distributor_pdb: | |||
| local podDisruptionBudget = $.policy.v1.podDisruptionBudget; | |||
There was a problem hiding this comment.
nit: should we use k.policy.v1.podDisruptionBudget for clarity? I see this usage in other files $.policy.v1.podDisruptionBudget, not sure how ksonnet-util/kausal.libsonnet contents ended up being at top-level
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Checklist
CONTRIBUTING.mdguide (required)featPRs are unlikely to be accepted unless a case can be made for the feature actually being a bug fix to existing behavior.docs/sources/setup/upgrade/_index.mddeprecated-config.yamlanddeleted-config.yamlfiles respectively in thetools/deprecated-config-checkerdirectory. Example PR