-
Notifications
You must be signed in to change notification settings - Fork 979
Make the name of the webhook certs more metallb specific #2244
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
Conversation
f66a7a6
to
9224d2e
Compare
@cyclinder mind checking the CI failures? I guess something went wrong. |
9224d2e
to
806beb2
Compare
sure, let me check these failures |
dbe0362
to
a6a670c
Compare
Hi @fedepaol, If we update the names of webhook_service/webhook_cert directly, this may be an incompatible change, which leads to failures with metallb-operator (the old manifests use the new docker-image, and the correct name is not specified in the controller via go flags). I think there are two ways:
I think 2 is enough, but I prefer 1, I like the default value to be metallb related. |
Can you fix https://github.com/metallb/metallb/blob/main/charts/metallb/charts/crds/templates/crds.yaml#L260 before everything else?
in out api-server. It was introduced here 5339a9a I think. Since the service was renamed from |
@cyclinder mind fixing the conflicts? |
6d1fb25
to
eaef2a7
Compare
eaef2a7
to
54151ec
Compare
Just a nit on the commit / PR title: here we are not making the name configurable, but fixing it to a metallb-only value. |
51cd7fd
to
fae7c06
Compare
make the names of the webhook and cert metallb specific to avoid name conflicts with other resources in the cluster. Signed-off-by: cyclinder <qifeng.guo@daocloud.io>
fae7c06
to
774bbf6
Compare
LGTM |
Rename webhook_service/webhook_cert name to avoid name conflicts with other resources in the cluster.
Fixes #2174