Skip to content
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

Watching specific namespaces and multiple operators running independently within a single cluster #190

Open
navoyan opened this issue Sep 20, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@navoyan
Copy link

navoyan commented Sep 20, 2024

Hi!
We have isolated (as much as possible) environments in our cluster that are deployed to different namespaces. The isolation is possible because all the operators we currently use are configured to watch only one namespace. That is, they do not steal the work of other operators in other namespaces, nor do they watch resource changes in other namespaces.

It seems impossible to achieve the same with the milvus operator. It makes cluster-scoped Kubernetes calls, which means that limiting it's permissions via namespaced RBAC won't do the trick.

Am I missing something? If not, is there any support for this feature planned?

@navoyan navoyan changed the title Watching specific namespaces and multiple operators running independently within a same cluster Watching specific namespaces and multiple operators running independently within a single cluster Sep 20, 2024
@haorenfsa
Copy link
Collaborator

You're right, It's not supported now. And no plan for this, since it seems not a very common requirement for community users.

You can make a patch to implement it though. There won't be much work in my consideration. You just need to add a flag, and make controller only watch the specified namespace.

@haorenfsa haorenfsa added the enhancement New feature or request label Sep 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants