-
Notifications
You must be signed in to change notification settings - Fork 465
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
Watch Namespaces based on labels and label selectors #9274
Comments
@sam-heilbron to look at this issue for scope/estimation. |
is this for tenancy? or for RBAC? i believe watch namespaces being a list allows us to use Roles instead of ClusterRoles |
This is for tenancy. If edge is installed with |
Zendesk ticket #3965 has been linked to this issue. |
This is in OSS v1.18.0-beta24 and v1.17.9 |
Gloo Edge Product
Enterprise
Gloo Edge Version
1.16.4
Is your feature request related to a problem? Please describe.
In GE, we currently either watch all namespaces, or we watch the namespaces configured in the
watchNamespaces
configuration. This is a very static setup. In a development environment, where you might use a namespace per PR, a more dynamic way of configuring which namespaces are being watched would provide the required flexibility (otherwise the GE config would need to be constantly updated).Note that we need to watch namespaces if we want to route to K8S services in Upstreams using EDS (i.e. using
kube
KubernetesUpstreamSpec
: https://docs.solo.io/gloo-edge/1.7.23/reference/api/github.com/solo-io/gloo/projects/gloo/api/v1/upstream.proto.sk/), as Gloo needs to be able to access the K8S endpoints in those namespaces.Describe the solution you'd like
Use K8S label selectors and labels on namespaces to dynamically add namespaces to GEs
watchNamespaces
.Describe alternatives you've considered
Regex based namespace selectors.
Additional Context
No response
Related Issues:
┆Issue is synchronized with this Asana task by Unito
The text was updated successfully, but these errors were encountered: