Apply Pod Security Standards at the Cluster Level - kubectl possible unintended alias problem #47081
Labels
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
priority/awaiting-more-evidence
Lowest priority. Possibly useful, but not yet enough support to actually get it done.
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 --".
The text was updated successfully, but these errors were encountered: