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.
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
kubectl get svc knative-ingressgateway -n istio-system and check output value for the EXTERNAL-IP @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 2hSteps to Reproduce the Problem
- follow install Minikube without a VM driver
- follow deploy helloworld go app
- run command
kubectl get svc knative-ingressgateway -n istio-systemand check output value for the EXTERNAL-IPAdditional 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.
@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}')
@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.
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.
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.
Most helpful comment
I don't know if this reply is too late, but I just went through this example myself. You need to do:
if you are using a minikube cluster. Note that port 32380 is the nodeport of the knative ingress gateway.