ray-project / ray-project/kuberay
[Feature] Authn and Authz support for KubeRay API server and CLI
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.7k
- Forks
- 866
- Avg merge
- 6d 14h
- Merged PRs (30d)
- 24
Description
Search before asking
- I had searched in the issues and found no similar feature requirement.
Description
There's no Authn and Authz support for KubeRay in the current design. Internally, we use GCP IAM role and k8s RBAC to manage user's access to k8s namespaces on GKE. I'm curious about what's KubeRay's plan regarding Authn and Authz story.
In our case, we don't expect users to interact with KubeRay API sever directly. API server will be used by our internal platform service and client, and they will handle the authn and authz.
On the other hand, users will be likely to use CLI to interact with Ray related resources. I wonder if KubeRay CLI could support k8s authn and authz, so they can only operate in their own namespaces.
Use case
When user runs ./kuberay cluster create/get/list/delete -n foo, kuberay should only allow users to perform the operations based on their permisions they have been granted in namespace foo, which should be identical as they use kubectl
Related issues
No response
Are you willing to submit a PR?
- Yes I am willing to submit a PR!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name specific files, tests, or entry points. First clarify the authentication and authorization scope for the API server and CLI, then define how CLI operations in a namespace should follow Kubernetes permissions; done means access is enforced consistently with kubectl.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- api, authentication, authorization, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100