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

[Bug] RBAC defined in Helm is out of sync with latest RBAC manifests #174

Closed
2 tasks done
ebr opened this issue Mar 7, 2022 · 0 comments · Fixed by #175
Closed
2 tasks done

[Bug] RBAC defined in Helm is out of sync with latest RBAC manifests #174

ebr opened this issue Mar 7, 2022 · 0 comments · Fixed by #175
Labels
bug Something isn't working

Comments

@ebr
Copy link
Contributor

ebr commented Mar 7, 2022

Search before asking

  • I searched the issues and found no similar issues.

KubeRay Component

ray-operator

What happened + What you expected to happen

RBAC manifests defined in ray-operator/config/rbac/role.yaml differs from those defined in the Helm chart: helm-chart/kuberay-operator/templates/role.yaml. This produces a lot of RBAC-related errors in the logs even with the latest build of the Operator, which may be hard for a user to troubleshoot.

Reproduction script

helm install kuberay-operator . --set rbacEnable=true
kubectl get clusterrole kuberay-operator -o yaml

Visually compare the diff between the deployed ClusterRole and the latest RBAC manifests. The live ClusterRole is missing key resources like ingress and recently added API groups such as coordination.k8s.io.

Anything else

No response

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant