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

kuberay-apiserver should match kuberay-operator in watchNamespaces feature #27

Open
shaoqin2 opened this issue Nov 22, 2023 · 0 comments

Comments

@shaoqin2
Copy link

# The KubeRay operator will watch the custom resources in the namespaces listed in the "watchNamespace" parameter.
# watchNamespace:
# - n1
# - n2

This is a very useful feature installing the operator, but kuberay-apiserver does not match this behavior when using singleNamespaceInstall.

If we install apiserver, operator in namespace X and operator with watchNamespac [X, Y], trying to manage CRD in Y, the setup leads to

2023/11/22 16:56:17 could not list clusters rpc error: code = Unknown desc = List clusters failed.: List RayCluster failed in tsray: rayclusters.ray.io is forbidden: User "system:serviceaccount:default:kuberay-apiserver" cannot list resource "rayclusters" in API group "ray.io" in the namespace "Y"

Should we consider also installing the RBAC for CRD in kuberay-apiserver to a list of watchNamespace like kuberay-operator?

I'm happy to provide that PR if maintainers believe this is a reasonable request

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant