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

Apply Pod Security Standards at the Cluster Level - kubectl possible unintended alias problem #47081

Open
brianjester opened this issue Jul 3, 2024 · 4 comments
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.

Comments

@brianjester
Copy link

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 --".

@k8s-ci-robot
Copy link
Contributor

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.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Jul 3, 2024
@tamilselvan1102
Copy link
Contributor

I think if add a note under [before you begin] section of this page would be more suitable.

@sftim
Copy link
Contributor

sftim commented Jul 4, 2024

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.

@sftim
Copy link
Contributor

sftim commented Jul 4, 2024

/priority awaiting-more-evidence

(about why we should change one specific page to remind people to undo something recommended on a different site)

@k8s-ci-robot k8s-ci-robot added the priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. label Jul 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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.
Projects
None yet
Development

No branches or pull requests

4 participants