-
Notifications
You must be signed in to change notification settings - Fork 697
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
Scope TFJob operator to only claim jobs in a given namespace #759
Comments
Looks like informer can be scoped to a namespace. But by default we monitor all namespaces So we need to add an option to monitor a namespace. I wonder if we can easily monitor a subset of namespaces? |
Argo workflow controller supports the notion of an "instance ID". The way it works is:
Here is the exact logic:
No, not easily. The REST API supports either cluster scoped queries, or namespaced scoped queries. To monitor N namespaces, you'll have to have to establish N watches. |
Thanks @jessesuen |
We'd like to be able to scope Kubeflow to a particular namespace to better support multi-tenant situations.
See kubeflow/kubeflow#1213
When deploying the operator we should be able to specify which namespaces to monitor and the operator should only claim/manage jobs in that namespace.
We'd also like to scope our RBAC permissions and service accounts to only the provided namespaces.
@gaocegege Any idea how this should be implemented? Do informers have an option to allow scoping to namespaces
@jessesuen I think Argo supports this; what do you do?
The text was updated successfully, but these errors were encountered: