-
Notifications
You must be signed in to change notification settings - Fork 39.4k
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
Add the option to bind to a different address with kubectl port-forward #29678
Comments
@spacepluk Would you be interested in implementing this feature? |
cc @pwittrock |
hi there, I'm a bit swamped right now but hopefully I'll have some time next week to give it a try. I already hacked the binding address to make it work for me, so it should only be a matter of figuring out how you manage the cli parameters and try to write some decent go :) |
@pwittrock i would be interested in implementing this feature. will send a pull request. |
@spacepluk if you have managed a workaround , it would be nice to share with the community :) |
I don't think #43692 is what you wanted? |
I'm sorry, my bad. It's #43962. |
MOving to #43962 as canonical bug |
Even a switch to bind to
0.0.0.0
would do the trick for me. My use case is debugging when the client needs to be in a Windows VM.The text was updated successfully, but these errors were encountered: