-
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
microk8s kubectl E_REQUISITE_NOT_FOUND #16048
Labels
kind/question
Questions that haven't been identified as being feature requests or bugs.
Comments
gnoejuan
added
the
kind/bug
Outline of a bug - must adhere to the bug report template.
label
Feb 16, 2020
che-bot
added
the
status/need-triage
An issue that needs to be prioritized by the curator responsible for the triage. See https://github.
label
Feb 16, 2020
|
tolusha
added
kind/question
Questions that haven't been identified as being feature requests or bugs.
and removed
kind/bug
Outline of a bug - must adhere to the bug report template.
labels
Feb 17, 2020
ibuziuk
added
status/analyzing
An issue has been proposed and it is currently being analyzed for effort and implementation approach
team/deploy
and removed
status/need-triage
An issue that needs to be prioritized by the curator responsible for the triage. See https://github.
labels
Feb 17, 2020
-a operator did the fix. Thank you very much! hmmm after rebooting, i had to "reimplement workaround 1". |
tolusha
removed
the
status/analyzing
An issue has been proposed and it is currently being analyzed for effort and implementation approach
label
Feb 17, 2020
In case somebody came across this thread from google: kubectl(){
minikube.kubectl "$@"
}
export -f kubectl should actually be: kubectl(){
microk8s.kubectl "$@"
}
export -f kubectl Not sure if I would have ran into the
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
chectl fails
✖ Verify if kubectl is installed
with E_REQUISITE_NOT_FOUNDChe version
chectl/7.8.0 linux-x64 node-v10.18.1
Steps to reproduce
sudo snap install microk8s --classic --channel=1.17/stable
bash <(curl -sL https://www.eclipse.org/che/chectl/)
microk8s.config | cat - > $HOME/.kube/config
After encountering connection refusedchectl server:start -m -p microk8s -a helm
Expected behavior
Chectl uses the microk8s.kubectl kubectl.
Runtime
kubectl version
)oc version
)minikube version
andkubectl version
)minishift version
andoc version
)docker version
andkubectl version
)Screenshots
Installation method
Environment
Additional context
It looks like chectl uses a repository called `command-exists. Looking at the code, it looks like command-exists simply sends commands to the command line. Chectl's implementation seems to only use command-exists.
So, I looked up how to use bash-aliases in a npm script and came across this stackoverflow solution https://askubuntu.com/a/98791 and implemented it like in my .bashrc :
EDIT: This was the original. Probably led to some of my problems. Look below for the correct addition to .bashrc
which still did not work
Edit: Should have been
The text was updated successfully, but these errors were encountered: