-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Improve kubeconfig injection with chectl #14877
Comments
@l0rd not sure about priority, but I put P1 for now, since having a neat kubeconfig support looks pretty important for kubenative IDE |
I confirm this should be a P1 |
PR for |
Issues go stale after Mark the issue as fresh with If this issue is safe to close now please do so. Moderators: Add |
Closing this issue as today we have a mechanism to pre-create secrets that will be automatically mounted in workspaces containers. |
Is your enhancement related to a problem? Please describe.
A working Kubernetes config is something that users will expect in a Che workspace but the UX is still not perfect:
Describe the solution you'd like
--context
to theworkspace:inject
command. It will be used to specify the context to be injected. If no--context
parameter is provided only the current context will be injected.--inject-context <>
and--inject-current-context
to theworkspace:start
command. Since theworkspace:start
command currently doesn't start a workspace (it only creates it), to inject the we should probably add init containers that will generate the kube config, create a secret with the user token and a config map with the other context details.workspace:inject
to use the init container approach mentioned above.The text was updated successfully, but these errors were encountered: