Skip to content
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

Allow configuration of webhook selectors #1063

Open
diversario opened this issue Feb 12, 2024 · 0 comments · May be fixed by #1172
Open

Allow configuration of webhook selectors #1063

diversario opened this issue Feb 12, 2024 · 0 comments · May be fixed by #1172
Labels
enhancement New feature or request

Comments

@diversario
Copy link

diversario commented Feb 12, 2024

Is your feature request related to a problem?

When standing up a new cluster provisioned by ArgoCD, there's a fairly high (~20% at least) chance that the mservice.elbv2.k8s.aws MHW, in a yet-non-functional state will block creation of Linkerd service objects, which in turn will block AWS LBC pods from being created, thus creating a deadlock.

Describe the solution you'd like
Fully configurable objectSelector blocks in webhookconfiguration should allow excluding certain services from the webhook.

Describe alternatives you've considered
Configuring linkerd MWH to exclude objects labeled with app.kubernetes.io/name: aws-load-balancer-controller. This worked, FWIW, but only because Linkerd's MHW configuration does allow the very customization I'm requesting here. This may not be the case for other webhooks myself or other people encounter in tandem with AWS LBC.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
1 participant