Problem to Solve
While the recent addition of watchNamespace is a great improvement, it currently limits the controller to either a single namespace or the entire cluster. In complex multi-tenant environments, we often need to manage resources across several specific namespaces simultaneously. Without support for multiple namespaces, we are forced to deploy multiple controller instances or rely on old feature "watchFilterValue".
Proposed Solution
To address this, I propose extending the watchNamespace functionality to support a collection of namespaces, for example via a comma-separated string. This would allow a single CAPOSC instance to monitor a specific subset of namespaces.
Additional Context
No response
Environment Details
- Kubernetes version (`kubectl version`):
- OS (`/etc/os-release`):
- Kernel (`uname -a`):
- cluster-api-provider-outscale version:
- cluster-api version:
- Install tools:
- Kubernetes distribution:
- Kubernetes distribution version:
Problem to Solve
While the recent addition of watchNamespace is a great improvement, it currently limits the controller to either a single namespace or the entire cluster. In complex multi-tenant environments, we often need to manage resources across several specific namespaces simultaneously. Without support for multiple namespaces, we are forced to deploy multiple controller instances or rely on old feature "watchFilterValue".
Proposed Solution
To address this, I propose extending the watchNamespace functionality to support a collection of namespaces, for example via a comma-separated string. This would allow a single CAPOSC instance to monitor a specific subset of namespaces.
Additional Context
No response
Environment Details