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

Add support for MutatingWebhookConfigurations, ValidatingWebhookConfigurations, and EndpointSlices #210

Closed
acmayberry opened this issue May 27, 2022 · 4 comments
Assignees
Labels
enhancement New feature or request

Comments

@acmayberry
Copy link

It would be great to run separate service meshes like Istio or Linkerd for each tenant, but I believe most would at least require access to the following cluster level resources:

MutatingWebhookConfigurations
ValidatingWebhookConfigurations
EndpointSlices

Having a proxied and ACL'd list of these for each tenant would be really useful to support a service mesh per tenant.

@acmayberry acmayberry changed the title Add support MutatingWebhookConfigurations, ValidatingWebhookConfigurations, and EndpointSlices Add support for MutatingWebhookConfigurations, ValidatingWebhookConfigurations, and EndpointSlices May 27, 2022
@oliverbaehler
Copy link
Collaborator

Might be possible with #185. I will keep you posted with the progress

@oliverbaehler oliverbaehler self-assigned this Feb 10, 2023
@oliverbaehler oliverbaehler added the enhancement New feature or request label Feb 10, 2023
@prometherion
Copy link
Member

prometherion commented Feb 10, 2023

I don't see any problem with the EndpointSlices, since it's namespaced.

NAME                              SHORTNAMES   APIVERSION                             NAMESPACED   KIND
endpointslices                                 discovery.k8s.io/v1                    true         EndpointSlice

We could add a new route for this, taking full advantage of the additional metadata for Services already supported by Capsule, which need to be documented.

Honestly, I'm not getting the point of MutatingWebhookConfigurations and ValidatingWebhookConfigurations: these are cluster-scoped resources that could impact potentially any other Namespace in the cluster.

May I ask you for a real use case to understand better your requirements?

@oliverbaehler
Copy link
Collaborator

Cluster-Scoped resources are introduced with this:

You can enable it with the --feature-gates=ProxyClusterScoped=true argument for the proxy and then creating your ACLs.

Namespaced-Scoped were introduced with this:

You can add the --feature-gates=ProxyAllNamespaced=true

Note these are currently both Alpha features but cover your requests use-case.

@prometherion
Copy link
Member

prometherion commented Jul 3, 2024

Closing due to inactivity and lack of response, besides the fact it's now supported.

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
Development

No branches or pull requests

3 participants