-
Notifications
You must be signed in to change notification settings - Fork 15
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
[Action] Create kubeconfig with read-only scope #18
Comments
Questions
|
I can work on this |
Wonderful, thank you @dipankardas011!
We can start with one-time manually to unblock contributors. It would then be great if you could suggest a process to automate this as part of this issue as well since clusters will be ephemeral :)
I think it's ok to have a cluster-wide access with clusterRole as long as it's read/list/watch only 👍 |
Also @nikimanoledaki can I assume we have the kubeconfig in some file or as a string type in any programmnig language? I was thinking of using golang to use the kubernetes-go client to create those but first I will try it out via manual process |
We need to give individual contributors read-only access to the cluster.
This can be done by creating a Role with “get”, ”watch”, ”list” permissions, create a ServiceAccount, then generate a kubeconfig for this.
The resources should be limited to Pods to begin with.
See here for a tutorial/example of how to do this.
The text was updated successfully, but these errors were encountered: