-
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
chectl inject should support oc CLI #15987
Comments
cc/ @nickboldt |
Will this be done in time for Che 7.9? I'm hoping so since we need this functionality for the camel-k devfile. |
@tolusha FYI |
An alternative is to check if |
@azatsarynnyy |
correct |
How can we need this for a devfile? Che/CRW-ctl might not even be present if Che is installed via operator, no? |
I don't think we support minishift anymore -- especially not for use with crwctl, which is officially supported ONLY for deploying to OCP 3.1 and airgapped/offline 4.x.
The camelk devfile's sidecar contains helm, kubectl and kamel. Can a user just run kubectl directly from within the workspace's sidecar's terminal? |
Sure, just open a Theia terminal into the sidecar and use CLI |
Also need to implement the command for Openshift case. |
Is your enhancement related to a problem? Please describe.
Currently,
chectl workspace inject -k
command useskubectl
to copy akubeconfig
file from local machine to the plugin sidecar. It was introduced in the PR che-incubator/chectl#33 and supposed to be used with Che deployed on minikube, with Che Kubernetes Plugin.chectl workspace inject -k
command may be also helpful with Che deployed on minishift. For that, it has be improved to useoc
CLI as well.Describe the solution you'd like
chectl may detect which platform is currently used (minikube/minishift) and use
kubectl
oroc
CLI.Describe alternatives you've considered
From Mario's comment:
Additional context
kubectl cp
command usage in chectl sources https://github.com/che-incubator/chectl/blob/1744186acbf0b78404cb1fd267e8ce1a9985144e/src/commands/workspace/inject.ts#L173The text was updated successfully, but these errors were encountered: