Improve kubeconfig injection with chectl

[l0rd]

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:

• A user cannot specify the particular kubernetes context (cluster, namespace and user) should be injectected.
• Starting a workspace with the local kubeconfig requires to run 2 commands (workspace start+inject) when it could be one command only.
• If a workspace is stopped and restarted the injected local kubeconfig will get lost.

Describe the solution you'd like

• Add the parameter --context to the workspace: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.
• Add two new parameter --inject-context <> and --inject-current-context to the workspace:start command. Since the workspace: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.
• Modify workspace:inject to use the init container approach mentioned above.

[l0rd]

cc @kameshsampath

[ibuziuk]

@l0rd not sure about priority, but I put P1 for now, since having a neat kubeconfig support looks pretty important for kubenative IDE

[l0rd]

I confirm this should be a P1

[azatsarynnyy]

PR for --context parameter che-incubator/chectl#430

[che-bot]

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

[l0rd]

Closing this issue as today we have a mechanism to pre-create secrets that will be automatically mounted in workspaces containers.