Skip to content

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

Open
AndrewKostka wants to merge 1 commit into
mainfrom
tunnel-via-kubectl
Open

chore(make): use kubectl port-forward for local cluster traffic#1681
AndrewKostka wants to merge 1 commit into
mainfrom
tunnel-via-kubectl

Conversation

@AndrewKostka
Copy link
Copy Markdown
Contributor

No description provided.

Comment thread Makefile

.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
Copy Markdown
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?

Comment thread Makefile
minikube-tunnel: # @HELP Open a tunnel to the local ingress via kubectl and expose it at port 80 on the host system
minikube-tunnel:
./bin/minikube-tunnel
sudo -E kubectl --context minikube-wbaas port-forward -n kube-system service/ingress-nginx-controller 80:80
Copy link
Copy Markdown
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
Copy Markdown
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