Closed
Description
NGINX Ingress controller version:0.25.0
quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.25.0
Kubernetes version (use kubectl version
): 1.10
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.11", GitCommit:"637c7e288581ee40ab4ca210618a89a555b6e7e9", GitTreeState:"clean", BuildDate:"2018-11-26T14:38:32Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.11", GitCommit:"637c7e288581ee40ab4ca210618a89a555b6e7e9", GitTreeState:"clean", BuildDate:"2018-11-26T14:25:46Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Environment:
- Cloud provider or hardware configuration: mac
- OS (e.g. from /etc/os-release):
sw_vers
ProductName: Mac OS X
ProductVersion: 10.14.5
BuildVersion: 18F132
- Kernel (e.g.
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
- Install tools:
Docker for Mac - Others:
What happened:
- follow the Docker for mac guide
- confirm nginx-ingress-controller deployment running
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.
Metadata
Metadata
Assignees
Labels
No labels