-
Notifications
You must be signed in to change notification settings - Fork 326
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
[NET-4144] add gateway pdb #2985
Conversation
- PDB for gateways
- PDB for gateways
- CHANGELOG.md
- added entry in .changelog folder
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Skimmed through the changes and have some basic questions. Will go through the PR again in detail once those queries get resolved.
- removed entry in .changelog folder - reverted changes in values.yaml done for local testing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good mostly. Deferring the approval to the service-mesh
/gateways
team who owns the codebase.
- correction in .changelog
Sorry to drop in out of nowhere! But any chance to add a pdb for the ingress gateways too? I know ingress gateways themselves are deprecated for replacement by api-gateways, but they are still supported. Its confusing if the gateways are inconsistent in their config, unless they're going to be removed from the chart completely. |
|
- added pdb to ingress gateways - correction in .changelog
.changelog/2985.txt
Outdated
@@ -0,0 +1,3 @@ | |||
```release-note:improvement | |||
pdb: adding pod disruption budget for all the gateways |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pdb: adding pod disruption budget for all the gateways | |
gateways: create PodDisruptionBudget for all gateways |
- modified all PDB configs to be homogenous. - added poddisruptionbudget.go for custom gateways. - correction in .changelog
} | ||
|
||
type PodDisruptionBudgetSpec struct { | ||
Enabled bool `json:"enabled,omitempty"` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wouldn't expect an Enabled
field here. If the field is non-nil then we can assume that it's enabled
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
my thought process was:
- The configs remain same for resources that we create and the resources created through templates. i.e. they all have - enable, minAvailable and maxUnavailable thus making them homogenous.
- For the resources we create, if the end-user/dev needs to disable PDB she/he could just go ahead and make enabled = false instead of deleting the whole stanza and adding it back again when they require it.
Shall I go ahead and remove the enabled flag anyways?
- updating PDB to follow the pattern in role.go
- updating PDB to follow the pattern in role.go
@nathancoleman I chatted with @kkavish he said this might need re-review? However I'm not sure if it's ready given that it looks like most of the tests are still failing? |
Re-reviewing is on my To Do list; however, it's lower in priority than work related to Consul 1.17.0 releasing next week. I confirmed with @kkavish that we're not trying to get this change into 1.17.0. |
Sure not a rush. Let's revisit after 1.17, I also asked @kkavish to brush up this PR to get the tests to pass as well. |
@kkavish Could you try re-basing to get the unit tests on control plane to pass? |
- disabling pdbs in values.yaml
- data plane image
- running tests
# Conflicts: # charts/consul/values.yaml
- running tests
- running tests
- running tests
- running tests
- running tests
- running tests
- running tests
I'm guess the PR is still failing to pass any acceptance tests? |
@david-yu sorry, I've been on a vacation, I'll try to get this fixed this week. |
- running tests
# Conflicts: # charts/consul/templates/crd-gatewayclassconfigs.yaml
- running tests
Changes proposed in this PR:
How I've tested this PR:
manually
How I expect reviewers to test this PR:
Checklist: