Update docs for minikube tunnel #47
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
docs update
What is the current behavior?
On my system, running
minikube tunnel, exposes the tunnel on the ip address192.168.49.2. HTTP Requests to that IP trip up nginx and just lead to 404 errors.I'm still a bloody beginner with kubernetes and it took me a long time to debug this. Adding this flag might prevent other beginners from running into the same issue.
What is the new behavior?
On my system, this just fixes the problem. Both
http://studio.localhostandhttp://localhostwork as expected.