Open brianjester opened 3 days ago
This issue is currently awaiting triage.
SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted
label.
The triage/accepted
label can be added by org members by writing /triage accepted
in a comment.
I think if add a note under [before you begin] section of this page would be more suitable.
This seems really specific. I think it'd be better to change the minikube docs to tell people to make a note to unalias kubectl, or (also good) to not set that alias - it is not needed.
/priority awaiting-more-evidence
(about why we should change one specific page to remind people to undo something recommended on a different site)
If the user has used minikube up to this point and followed the recommendation to alias kubectl to "minikube kubectl --" mentioned on the "minikube start" page here: https://minikube.sigs.k8s.io/docs/start/?arch=%2Fmacos%2Fx86-64%2Fstable%2Fbinary+download
...then the "kubectl" command will not work with the "kind" created cluster because each time they run "kubectl" it will be running the aliased "minikube kubectl --" command instead.
Recommend a note to remind the 1st time user that if they have previously aliased kubectl command to work with minikube they'll need to unalias or remove that alias so they are using the "native" kubectl command and not the aliased "minkube kubestl --".