-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
⚠️ Run webhooks with managers #3985
⚠️ Run webhooks with managers #3985
Conversation
/milestone v0.4.0 |
/hold |
# This configuration is for teaching kustomize how to update name ref and var substitution | ||
varReference: | ||
- kind: Deployment | ||
path: spec/template/spec/volumes/secret/secretName |
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.
Is this actually needed? I feel like this was something that we previously used to hack together the separate manager and webhook deployments. I'm not seeing this in the upstream kubuebuilder examples: https://github.com/kubernetes-sigs/kubebuilder/tree/63b35350fe8b4d133c0bdb8fdd9a9a61fe30ac61/testdata/project-v3/config/default
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.
This is not in the kubuilder example, but I felt that we are on the safe path if we ensure all the webhook services get a different name for each provider, so during the reshuffle I preserved:
secretName: $(SERVICE_NAME)-cert # this secret will not be prefixed since it's not managed by kustomize
in bootstrap/kubeadm/config/certmanager/certificate.yaml
and made the necessary changes for it being resolved in config/default/kustomize.yaml
which basically consist of creating this file and referencing it
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.
would be good to also describe these changes in https://github.com/kubernetes-sigs/cluster-api/blob/master/docs/book/src/developer/providers/v1alpha3-to-v1alpha4.md
51427d3
to
c2c839a
Compare
Done! |
/test pull-cluster-api-e2e-full-main |
/test pull-cluster-api-e2e-full-main |
LGTM pending squash |
2b9da96
to
df4014d
Compare
@vincepri squashed! |
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.
/lgtm
/assign @CecileRobertMichon @detiber
for approval
/test pull-cluster-api-e2e-full-main |
a196908
to
3533800
Compare
/test pull-cluster-api-e2e-full-main |
rebase & fixed error on machine pools test |
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.
/lgtm
/assign @detiber @CecileRobertMichon
/lgtm |
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.
lgtm overall
sorry for not getting to this earlier @fabriziopandini
3533800
to
fa9edea
Compare
Rebased + adressed @CecileRobertMichon comments |
fa9edea
to
280db9a
Compare
/test pull-cluster-api-e2e-full-main |
/test pull-cluster-api-e2e-full-main The panic should be resolved in 1.21 |
/test pull-cluster-api-test-main |
/retest |
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.
/lgtm
/retest |
@fabriziopandini: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
/retest |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: CecileRobertMichon The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What this PR does / why we need it:
Given that #3042 for v1alpha4 requires single controllers managing all namespaces, this PR moves the webhooks back in the main manager and run them behind RBAC in case we'll need a client in the future.
Which issue(s) this PR fixes:
Fixes #3822