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

Generate separate consumer kubeconfig per user/team #1276

Open
Tracked by #683
devdattakulkarni opened this issue May 14, 2024 · 0 comments
Open
Tracked by #683

Generate separate consumer kubeconfig per user/team #1276

devdattakulkarni opened this issue May 14, 2024 · 0 comments

Comments

@devdattakulkarni
Copy link
Contributor

devdattakulkarni commented May 14, 2024

KubePlus generates a consumer kubeconfig which can be used by users to create application instances in a self-service manner. Currently, only one consumer kubeconfig is generated by KubePlus. We should support the creation of separate kubeconfig files for different user/teams. Each team should be able to access only their application instance and no one else's.

One way to achieve this will be to tie the consumer kubeconfig to the Namespace. However, in the current model, an application Namespace is created at runtime.

Note that previously KubePlus supported deploying applications in existing Namespaces. But we went away from that model for simplicity reasons. Let's revisit that model as part of this feature.

We have to add a kubectl plugin to generate consumer kubeconfig
kubectl generate consumer kubeconfig <Namespace>

As part of generating the kubeconfig, we should grant the new SA permissions on *.platformapi.kubeplus APIs.

@devdattakulkarni devdattakulkarni mentioned this issue May 14, 2024
16 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant