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.

Sign up for GitHub

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

Jump to bottom

Issue with k8s.io/docs/tasks/access-application-cluster/ingress-minikube/ #16503

Closed
FredericLatour opened this issue Sep 22, 2019 · 6 comments
Closed

Issue with k8s.io/docs/tasks/access-application-cluster/ingress-minikube/ #16503

FredericLatour opened this issue Sep 22, 2019 · 6 comments
Labels
priority/backlog Higher priority than priority/awaiting-more-evidence.

Comments

@FredericLatour
Copy link

This is a Bug Report

I'm following the instructions on the page and and curl hello-world.info doesn't give the expected result.

Problem:
After following the instructions, when I curl hello-world.info, I get the following result:

$ curl -k hello-world.info
<html>
<head><title>404 Not Found</title></head>
<body>
<center><h1>404 Not Found</h1></center>
<hr><center>openresty/1.15.8.1</center>
</body>
</html>

I can confirm that the deployment and service work correctly. Accessing the service via:
minikube service web --url
output the expected result (as described in the documentation).

Proposed Solution:
No idea but I have a hard time to understand how it can be so difficult to set up a kubernetes dev env with minikube.
No one minikube/ingress example I could find seem to work properly, at least on my minikube installation.

Page to Update:
https://kubernetes.io/...

Kubernetes Version:
Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.6", GitCommit:"96fac5cd13a5dc064f7d9f4f23030a6aeface6cc", GitTreeState:"clean", BuildDate:"2019-08-19T11:13:49Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.2", GitCommit:"f6278300bebbb750328ac16ee6dd3aa7d3549568", GitTreeState:"clean", BuildDate:"2019-08-05T09:15:22Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"}
@sftim
Copy link
Contributor

sftim commented Sep 23, 2019

The current page suggests

Add the following line to the bottom of the /etc/hosts file.
Note: If you are running Minikube locally, use minikube ip to get the external IP. The IP address displayed within the ingress list will be the internal IP.

It sounds possible to clarify that, helping readers clearly understand what steps to follow so that the subsequent curl command works OK.

/priority backlog

@k8s-ci-robot k8s-ci-robot added the priority/backlog Higher priority than priority/awaiting-more-evidence. label Sep 23, 2019
@FredericLatour
Copy link
Author

@sftim I should had mentioned that I had indeed updated my Hosts file. I was able to ping hello-world.info and get a reponse from minikube ip.
And yes, I'm aware of the minikube ip command.
Just to be sure, I will re-play the page instructions once more.

@sftim
Copy link
Contributor

sftim commented Sep 23, 2019

@FredericLatour if you can clarify what needs to change on the page to get it right, that'll help a lot towards a fix.

@FredericLatour
Copy link
Author

@sftim It works now. It seems that the page was updated today and that the reason it was not working was because there was no base path. (that is hello-world.info/whatever would have worked properly)
On a different note: do you know why when I access hello-world ingress does not seem to automatically redirect to https whereas it is the case each time I tried to set up a site of mine?

@sftim
Copy link
Contributor

sftim commented Sep 23, 2019

Thanks for the update @FredericLatour
You can get more help via Stack Overflow, from the Kubernetes Slack organization, or the Discuss Kubernetes forum.

Fixed via #16458
/close

@k8s-ci-robot
Copy link
Contributor

@sftim: Closing this issue.

In response to this:

Thanks for the update @FredericLatour
You can get more help via Stack Overflow, from the Kubernetes Slack organization, or the Discuss Kubernetes forum.

Fixed via #16458
/close

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/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@FredericLatour @k8s-ci-robot @sftim