-
Notifications
You must be signed in to change notification settings - Fork 48
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
✨ Distinct webhook deployments #757
base: main
Are you sure you want to change the base?
Conversation
5bb8b75
to
68b8aca
Compare
This path introduces distinct webhook deployments for the admission and conversion webhooks. This is to provide a more stable and performant experience. The webhook pods will not require nearly as much memory as the controller-manager pods. Additionally, if the webhooks ever go down, it is a bad time. Admission webhooks being unavailable means no one can apply any changes to the VM Op APIs. The conversion webhooks being offline means no one can even *read* the VM Op APIs.
68b8aca
to
877034e
Compare
Minimum allowed line rate is |
Overall looks good to me from upgrade perspective. Shouldn't be any port conflict since we don't explicitly delete any deployment and re-deploy with the same port. We should test upgrade path from last release to main with this change for verification. One minor thing: should add two new deployment names here when validating component health during upgrade: https://gitlab-vmw.devops.broadcom.net/core-build/cayman_vm-operator/-/blob/vmware-main/vm-operator/wcp_patch/upgrade/gc_component_upgrade.py#L20 Thanks for the change. |
What does this PR do, and why is it needed?
This path introduces distinct webhook deployments for the admission and conversion webhooks. This is to provide a more stable and performant experience. The webhook pods will not require nearly as much memory as the controller-manager pods. Additionally, if the webhooks ever go down, it is a bad time. Admission webhooks being unavailable means no one can apply any changes to the VM Op APIs. The conversion webhooks being offline means no one can even read the VM Op APIs.
This patch also removes the vestigial use of kustomizeconfig files since they are no longer needed, having been replaced by, well, the replacements feature.
Which issue(s) is/are addressed by this PR? (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes
NA
Are there any special notes for your reviewer:
We need to:
For a full list of the changes this PR introduces, please follow the steps below:
Generate the
config/local/infrastructure-components-original.yaml
andconfig/local/infrastructure-components.yaml
files to compare them:Once the two files have been generated, compare them with:
The
diff
should look just like the following:Please add a release note if necessary: