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

Add new workspace:inject --kubeconfig command #31

Closed
l0rd opened this issue Dec 21, 2018 · 0 comments · Fixed by #33
Closed

Add new workspace:inject --kubeconfig command #31

l0rd opened this issue Dec 21, 2018 · 0 comments · Fixed by #33

Comments

@l0rd
Copy link
Collaborator

l0rd commented Dec 21, 2018

The command syntax:

Inject configurations and tokens in a Che Workspace

USAGE
  $ chectl workspace:inject

OPTIONS
  -k, --kubeconfig                  Inject the local Kubernetes configuration
  -h, --help                        show CLI help
  -w, --workspace=workspaceid       Target workspace
  -c, --container=containerid      [default: dev] Target container
  -n, --chenamespace=chenamespace   [default: kube-che] Kubernetes namespace where the workspace is deployed

When the command is executedchectl should look at local ~/.kube/config and:

  • generate a new ~/.kube/config to copy it in the target container
  • copy certificates and keys in the target container

More details about the expected behaviour of the command:

  • If a ~/.kube/config already exist in the target container the command should fail (we may later add a --force flag but that's not in the scope of this issue)
  • The --workspace flag can be omitted only if there is just one running workspace (if will fail otherwise)
  • If the --container flag is omitted the default container should be the che-dev (it will fail if che-dev doesn't exist)
@l0rd l0rd changed the title Add new workspace:inject command to add the kube config in a running workspace Add new workspace:inject --kubeconfig command Dec 21, 2018
@slemeur slemeur mentioned this issue Dec 21, 2018
69 tasks
@azatsarynnyy azatsarynnyy pinned this issue Dec 30, 2018
@azatsarynnyy azatsarynnyy unpinned this issue Dec 30, 2018
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

Successfully merging a pull request may close this issue.

1 participant