You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Having a proxied and ACL'd list of these for each tenant would be really useful to support a service mesh per tenant.
The text was updated successfully, but these errors were encountered:
acmayberry
changed the title
Add support MutatingWebhookConfigurations, ValidatingWebhookConfigurations, and EndpointSlices
Add support for MutatingWebhookConfigurations, ValidatingWebhookConfigurations, and EndpointSlices
May 27, 2022
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?
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.
The text was updated successfully, but these errors were encountered: