Open bcollard opened 2 years ago
Similar request to https://github.com/solo-io/gloo/issues/3173
Related and similar to https://github.com/solo-io/gloo/issues/6871
@jackstine What's the difference between this issue and #6871? Is there any date we can expect any of these two issues resolved?
@pmichna this is more focused on namespaces Or, at least, expose a "deny list" of namespaces to watch. While #6871 is more focused on labels.
Adding information about Field Selectors https://kubernetes.io/docs/concepts/overview/working-with-objects/field-selectors/
Zendesk ticket #1051 has been linked to this issue.
This issue has been marked as stale because of no activity in the last 180 days. It will be closed in the next 180 days unless it is tagged "no stalebot" or other activity occurs.
Version
1.10.x (latest stable)
Is your feature request related to a problem? Please describe.
Currently, the Gloo controllers watch the Gloo CRs (VS, AC, US, etc.) in all the namespaces declared under
watchNamespaces
(all NS by default).The goal is to control this "watchable" scope with labels.
Or, at least, expose a "deny list" of namespaces to watch. We have customers with a large list of namespaces, unable to keep that
watchNamespaces
list up to date. But they know which NS they don't want to watch. Btw. thekube-system
namespace was a source of noise for the Gloo controllers.Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional Context
No response