Support for multiple namespaces for watchNamespace argument

[herrbpl]

Is your feature request related to a problem?
Currently it is possible only to specify single namespace to watch. Or leave value unspecified to watch all namespaces. But sometimes more flexibility is needed. Like watching 2 or three namespaces but not all.

Describe the solution you'd like
Change watchNamespace option to stringList and watch multiple namespaces with single instance

Describe alternatives you've considered
I considered adding multiple instances running with different configuration but this is no go because this adds requirement to create multiple LB-s instead of having one.

[kishorj]

@herrbpl, the watchNamespace feature is provided by controller-runtime and currently it doesn't support multiple namespaces. What is your use-case for multiple namespaces?

[herrbpl]

Hi. For example we have case where we don't want users to give direct access to create AWS objects via service or ingress objects, we actually use NGINX ingress controller behind ALB (created/configured via AWS LB Controller) but for system apps we might need to create AWS objects from more than one namespace (ie, ALB for NINGX ingress, another ALB for ArgoCD etc). So there are lot of cases where you want to limit list of watched namespaces but not to single namespace only.

I understand if this introduces some additional work however, it should be pretty standard stuff to watch multiple namespaces instead of all/single. Hope you can take it into works.

[kishorj]

@herrbpl, in v2.5.0 release, we plan to support running multiple controller deployments in the cluster - this will allow you to have a specific controller watch a particular namespace. Feature #2185.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.