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

chore(make): use kubectl port-forward for local cluster traffic #1681

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

AndrewKostka
Copy link
Contributor

No description provided.

@@ -39,9 +39,9 @@ minikube-dashboard:
minikube --profile minikube-wbaas dashboard

.PHONY: minikube-tunnel
minikube-tunnel: # @HELP Open a tunnel to the local cluster and expose it on an IP on the host system
minikube-tunnel: # @HELP Open a tunnel to the local ingress via kubectl and expose it at port 80 on the host system
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe it would make sense to introduce a new target to be called like make minikube-port-forward or something?

minikube-tunnel:
./bin/minikube-tunnel
sudo -E kubectl --context minikube-wbaas port-forward -n kube-system service/ingress-nginx-controller 80:80
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

unfortunately this doesn't work for me: I get error: context "minikube-wbaas" does not exist since kubectl run with sudo doesn't share contexts with my user

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sudo kubectl config get-contexts returns no contexts

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants