-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
[bitnami/kuberay] Adding the list and watch for endpoints resource to the cluster role to solve #30648 #31226
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Francisco Rivas <[email protected]>
Re-opening. Sorry for the delay with this. I hope you have had a Merry Christmas and a Happy New Year and the 3 Kings had been great to you. I have synched my fork and it should be fine now. Thank you very much for all the support and lets get this through! |
Thanks for your contribution! Could you please bump the chart version in the Chart.yaml? This is necessary to test the changes and cut a new release. |
Signed-off-by: Francisco Rivas <[email protected]>
Signed-off-by: Bitnami Containers <[email protected]>
Signed-off-by: Bitnami Containers <[email protected]>
Hello @carrodher and @alvneiayu I hope you are doing great! I was wondering about this PR. I have seen there are 2 new releases of Kuberay solving other important issues. I was wondering if this one will be included in a future release. Thank you for your support and help Thank you very much! |
Signed-off-by: Carlos Rodríguez Hernández <[email protected]>
Signed-off-by: Bitnami Containers <[email protected]>
This change adds the necessary rules to the operator cluster role to get the Ray Service in Running state and also make the kuberay operator not to show the
This issue has been seen in the operator's log and as I am not using the apiserver or cluster components
Description of the change
Adds RBAC rules to the Operator Cluster Role.
Benefits
Ray Service will be in running state and also the Operator logs won't show the messages with the permissions.
Possible drawbacks
None as far as I know. Just keep in mind this applies only to the operator not apiserver or cluster.
Applicable issues