You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
cc-backend ➤ kubectl get pods -n ingress-nginx
NAME READY STATUS RESTARTS AGE
nginx-ingress-controller-54f689bd-64sp5 1/1 Running 0 6h
cc-backend ➤ kubectl get deployment -n ingress-nginx
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
nginx-ingress-controller 1 1 1 1 6h
The Address field is null and localhost is unreachable.
cc-backend ➤ kubectl describe ingress
Name: simple-fanout-example
Namespace: default
Address:
Default backend: default-http-backend:80 (<none>)
Rules:
Host Path Backends
---- ---- --------
*
/apple apple-service:5678 (<none>)
/banana banana-service:5678 (<none>)
Annotations:
nginx.ingress.kubernetes.io/rewrite-target: /
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal CREATE 54m nginx-ingress-controller Ingress default/simple-fanout-example
cc-backend ➤ curl -kL http://localhost
curl: (7) Failed to connect to localhost port 80: Connection refused
kubectl get svc -n ingress-nginx
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
ingress-nginx LoadBalancer 10.96.200.3 <pending> 80:31036/TCP,443:32756/TCP 1d
#2415 mentioned the problem that Nginx Ingress does not route on. The after following the mac guide the problem seems to be resolved. So it is not the same as mine.
What you expected to happen:
nginx-ingress-controller can forward http request correctly.
The text was updated successfully, but these errors were encountered:
NGINX Ingress controller version:0.25.0
quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.25.0
Kubernetes version (use
kubectl version
): 1.10Environment:
uname -a
):Darwin Kernel Version 18.6.0: Thu Apr 25 23:16:27 PDT 2019; root:xnu-4903.261.4~2/RELEASE_X86_64 x86_64
Docker for Mac
What happened:
#2415 mentioned the problem that Nginx Ingress does not route on. The after following the mac guide the problem seems to be resolved. So it is not the same as mine.
What you expected to happen:
nginx-ingress-controller can forward http request correctly.
The text was updated successfully, but these errors were encountered: