-
Notifications
You must be signed in to change notification settings - Fork 724
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
Missing Jaxjobs in aggregation ClusterRole #2416
Comments
Thank you for creating this @DnPlas, great catch! Yes, we should update the RBAC. @DnPlas @sandipanpanda Please can you create the hot fix at |
/remove-label lifecycle/needs-triage |
/good-first-issue |
@andreyvelich: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
This commit adds jaxjobs to the aggregation ClusterRole for Kubeflow, which allows Kubeflow Profiles to have edit and admin rights over this CR. Fixes kubeflow#2416
This commit adds jaxjobs to the aggregation ClusterRole for Kubeflow, which allows Kubeflow Profiles to have edit and admin rights over this CR. Fixes kubeflow#2416 Signed-off-by: Daniela Plascencia <[email protected]>
#2417 sent! |
) This commit adds jaxjobs to the aggregation ClusterRole for Kubeflow, which allows Kubeflow Profiles to have edit and admin rights over this CR. Fixes #2416 Signed-off-by: Daniela Plascencia <[email protected]>
Fixed in #2417 |
What happened?
Looks like
jaxjobs
are missing from thekubeflow-training-roles.yaml
because when I tested the ability to createjaxjobs
as a Kubeflow Profile in the profile's namespace, I got:After adding the
jaxjobs
in the aforementioned ClusterRole, I get:What did you expect to happen?
The Kubeflow profiles to have permissions to:
JaxJobs
Environment
Kubernetes version:
Training Operator version:
$ kubectl get pods -n kubeflow -l control-plane=kubeflow-training-operator -o jsonpath="{.items[*].spec.containers[*].image}" kubeflow/training-operator:v1-5170a
Impacted by this bug?
Give it a 👍 We prioritize the issues with most 👍
The text was updated successfully, but these errors were encountered: