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

Not getting EXTERNAL-IP after proper installation of KNative with Minikube and Istio (without a VM driver) #338

Closed
erandiganepola opened this issue Aug 20, 2018 · 5 comments

Comments

@erandiganepola
Copy link

@erandiganepola erandiganepola commented Aug 20, 2018

Expected Behavior

After installing Minikube and creating Cluster properly as per the KNative doc, Istio is installed to the cluster properly (verified by checking the status and it was running without any issues).
To deploy the sample helloworld.go app as given in the doc external IP is required.

External IP sould be given for the following commend as per the document.kubectl get svc knative-ingressgateway -n istio-system.

Actual Behavior

For the above scenario, I didn't get the external IP for the command kubectl get svc knative-ingressgateway -n istio-system.

Result got:

kubectl get svc knative-ingressgateway -n istio-system
NAME                     TYPE       CLUSTER-IP     EXTERNAL-IP   PORT(S)                                      AGE
knative-ingressgateway   NodePort   10.111.6.191   <none>        80:32380/TCP,443:32390/TCP,32400:32400/TCP   2h

Steps to Reproduce the Problem

  1. follow install Minikube without a VM driver
  2. follow deploy helloworld go app
  3. run command kubectl get svc knative-ingressgateway -n istio-system and check output value for the EXTERNAL-IP

Additional Info

@knative-prow-robot

This comment has been minimized.

Copy link

@knative-prow-robot knative-prow-robot commented Aug 20, 2018

@erandiganepola: GitHub didn't allow me to assign the following users: user.

Note that only knative members and repo collaborators can be assigned.
For more information please see the contributor guide

In response to this:

Expected Behavior

After installing Minikube and creating Cluster properly as per the KNative doc, Istio is installed to the cluster properly (verified by checking the status and it was running without any issues).
To deploy the sample helloworld.go app as given in the doc external IP is required.

External IP sould be given for the following commend as per the document.kubectl get svc knative-ingressgateway -n istio-system.

Actual Behavior

For the above scenario, I didn't get the external IP for the command kubectl get svc knative-ingressgateway -n istio-system.

Result got:

kubectl get svc knative-ingressgateway -n istio-system
NAME                     TYPE       CLUSTER-IP     EXTERNAL-IP   PORT(S)                                      AGE
knative-ingressgateway   NodePort   10.111.6.191   <none>        80:32380/TCP,443:32390/TCP,32400:32400/TCP   2h

Steps to Reproduce the Problem

  1. follow install Minikube without a VM driver
  2. follow deploy helloworld go app
  3. run command kubectl get svc knative-ingressgateway -n istio-system and check output value for the EXTERNAL-IP

Additional Info

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.

@samodell

This comment has been minimized.

Copy link
Contributor

@samodell samodell commented Aug 20, 2018

@erandiganepola I may be wrong, but it's my current understanding that you won't get an external-IP showing up for your service if you're using MiniKube, so this may be WAI.

There's a note at the bottom of the Minikube instructions for how to get a usable IP; does the provided command return a valid value for you?

echo $(minikube ip):$(kubectl get svc knative-ingressgateway -n istio-system -o 'jsonpath={.spec.ports[?(@.port==80)].nodePort}')

@erandiganepola

This comment has been minimized.

Copy link
Author

@erandiganepola erandiganepola commented Aug 21, 2018

@samodell Thank you very mcuh for your reply. I did use this command

echo $(sudo minikube ip):$(kubectl get svc knative-ingressgateway -n istio-system -o 'jsonpath={.spec.ports[?(@.port==80)].nodePort}')

Then received the result as 10.100.7.27:32380.

I used following command to make the request to the app : curl -H "Host: helloworld-go.default.example.com" http://10.100.7.27:80 (80 is the port mapping)

But didn't get the expected response. Then I checked for the docker container I created with this scenario (docker ps | grep {name}). It wasn't up. Please help if you have any idea regarding this.

@erandiganepola

This comment has been minimized.

Copy link
Author

@erandiganepola erandiganepola commented Aug 21, 2018

I followed the docs mentioned above for the path of running without a VM driver properly. But couldn't run the samples and get the expected results.

Finally I tried with a VM driver (virtualbox) and then was able to run the samples.

I guess docs are misleading when considering the flow of Installing without a VM. Please update docs.

@huang195

This comment has been minimized.

Copy link

@huang195 huang195 commented Aug 30, 2018

I don't know if this reply is too late, but I just went through this example myself. You need to do:

curl -H "Host: helloworld-go.default.example.com" http://10.100.7.27:32380

if you are using a minikube cluster. Note that port 32380 is the nodeport of the knative ingress gateway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.