Ingress not working

Ingress is not working and I am not sure why.
Details:
I have two deployments running four pods:
- i@cp:~$ k get pods -n prod
- NAME READY STATUS RESTARTS AGE
- hello-dep-58d75f88f-75j9w 1/1 Running 0 6m47s
- hello-dep-58d75f88f-tsjq6 1/1 Running 0 2d4h
- hello2-dep-6df5f875d6-fjlgx 1/1 Running 0 2d4h
- hello2-dep-6df5f875d6-rg8xf 1/1 Running 0 6m47s
And their respective services:
- i@cp:~$ k get svc -n prod
- NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
- hello-srv ClusterIP 10.107.219.251 <none> 80/TCP 2d4h
- hello2-srv ClusterIP 10.110.36.35 <none> 80/TCP 2d4h
I have created an ingress:
- i@cp:~$ k get ing -n prod
- NAME CLASS HOSTS ADDRESS PORTS AGE
- hello-ingress nginx hello.com 80 2d4h
- i@cp:~$ k describe ing -n prod
- Name: hello-ingress
- Labels: <none>
- Namespace: prod
- Address:
- Ingress Class: nginx
- Default backend: <default>
- Rules:
- Host Path Backends
- ---- ---- --------
- hello.com
- /v1 hello-srv:80 (192.168.0.121:8080,192.168.0.144:8080)
- /v2 hello2-srv:80 (192.168.0.244:8080,192.168.0.49:8080)
- Annotations: <none>
- Events:
- Type Reason Age From Message
- ---- ------ ---- ---- -------
- Normal Sync 3m48s nginx-ingress-controller Scheduled for sync
Curling any of the addresses works just fine:
- i@cp:~$ curl 192.168.0.121:8080
- Hello, world!
- Version: 1.0.0
- Hostname: hello-dep-58d75f88f-tsjq6
But the port 80 is closed:
- i@cp:~$ curl hello.com
- curl: (7) Failed to connect to hello.com port 80 after 0 ms: Connection refused
- i@cp:~$ curl hello.com/v1
- curl: (7) Failed to connect to hello.com port 80 after 0 ms: Connection refused
- i@cp:~$ curl localhost
- curl: (7) Failed to connect to localhost port 80 after 0 ms: Connection refused
- i@cp:~$ ping hello.com
- PING hello.com (192.168.138.129) 56(84) bytes of data.
- 64 bytes from k8scp (192.168.138.129): icmp_seq=1 ttl=64 time=0.083 ms
- i@cp:~$ curl k8scp
- curl: (7) Failed to connect to k8scp port 80 after 0 ms: Connection refused
- i@cp:~$ curl 192.168.138.129
- curl: (7) Failed to connect to 192.168.138.129 port 80 after 0 ms: Connection refused
I thought it was a problem of a lack of an Ingress Controller, so I installed one:
- i@cp:~$ helm list
- NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
- myingress default 1 2024-09-23 22:03:56.346203937 +0000 UTC deployed ingress-nginx-4.11.2 1.11.2
- i@cp:~$ k get pods
- NAME READY STATUS RESTARTS AGE
- myingress-ingress-nginx-controller-bxwpv 1/1 Running 0 47h
- myingress-ingress-nginx-controller-xrlxc 1/1 Running 2 (8m59s ago) 47h
But the result is the same.
What can be happening? Do I have to link the ingress Controller to my ingress somehow?
Thanks.
Comments
-
curl -H "Host: hello.com" $CLUSTER_IP/v1
0 -
The cluster IPs work. What I need is to access the ingress.
I have "hello.com" configured to point to the control plane.0 -
Hi @ilmx,
For external access, either use a NodePort Service for the ingress controller, or enable the hostPort on the myingress ingress controller Pods.
Regards,
-Chris0 -
Thanks @chrispokorni What does it mean "enable the hostPort on the myingress ingress controller Pods"? How can I do that?
In other clusters I have used (already installed), ingress used to work automatically so probably I am missing some step0 -
Mmmm... I have tried to create a NodePort, but I am not sure I understood how it should be created:
- ---
- apiVersion: v1
- kind: Service
- metadata:
- name: hello-nodeport
- namespace: prod
- spec:
- type: NodePort
- ports:
- - appProtocol: http
- name: http
- nodePort: 80
- port: 80
- protocol: TCP
- targetPort: http
- - appProtocol: https
- name: https
- nodePort: 443
- port: 443
- protocol: TCP
- targetPort: https
- selector:
- app.kubernetes.io/name: myingress-ingress-nginx-controller
This fails with:
- Invalid value: 80: provided port is not in the valid range. The range of valid ports is 30000-32767
But I would like to use port 80 to access the ingress service that will route to my cluster IP.
0 -
Hi @ilmx,
In order to expose your ingress controller on port 80 you would need to verify that
hostPort: 80
is declared in themyingress-ingress-nginx-controller
manifest. If it is not, then declare it. Assuming you closely followed the ingress deployment and selected the DaemonSet controller in the chart'svalues.yaml
manifest, you could simply edit the controller object with:- kubectl edit daemonset myingress-ingress-nginx-controller
Otherwise you could enable the
hostPort
in the chart'svalues.yaml
manifest.The
hostPort
set on the ingress controller Pod allows the ingress proxy to capture traffic on port 80 and forward it to either of the Servicesweb-one
orweb-two
exposing their respective webserver Deployments. This method allows Pods to directly map to a port of the host, without the need for the NodePort Service.Discover more about the
hostPort
:- kubectl explain --recursive pod.spec.containers.ports
- kubectl explain --recursive pod.spec.containers.ports.hostPort
Regards,
-Chris0
Categories
- All Categories
- 139 LFX Mentorship
- 139 LFX Mentorship: Linux Kernel
- 816 Linux Foundation IT Professional Programs
- 367 Cloud Engineer IT Professional Program
- 184 Advanced Cloud Engineer IT Professional Program
- 83 DevOps Engineer IT Professional Program
- 151 Cloud Native Developer IT Professional Program
- 143 Express Training Courses & Microlearning
- 143 Express Courses - Discussion Forum
- Microlearning - Discussion Forum
- 6.6K Training Courses
- 48 LFC110 Class Forum - Discontinued
- 72 LFC131 Class Forum
- 49 LFD102 Class Forum
- 234 LFD103 Class Forum
- 21 LFD110 Class Forum
- 44 LFD121 Class Forum
- 1 LFD123 Class Forum
- LFD125 Class Forum
- 18 LFD133 Class Forum
- 8 LFD134 Class Forum
- 18 LFD137 Class Forum
- 72 LFD201 Class Forum
- 5 LFD210 Class Forum
- 5 LFD210-CN Class Forum
- 2 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum - Discontinued
- 2 LFD233 Class Forum
- 4 LFD237 Class Forum
- 24 LFD254 Class Forum
- 719 LFD259 Class Forum
- 111 LFD272 Class Forum - Discontinued
- 4 LFD272-JP クラス フォーラム
- 13 LFD273 Class Forum
- 245 LFS101 Class Forum
- 2 LFS111 Class Forum
- 3 LFS112 Class Forum
- 3 LFS116 Class Forum
- 7 LFS118 Class Forum
- LFS120 Class Forum
- 9 LFS142 Class Forum
- 8 LFS144 Class Forum
- 4 LFS145 Class Forum
- 4 LFS146 Class Forum
- 16 LFS148 Class Forum
- 15 LFS151 Class Forum
- 5 LFS157 Class Forum
- 68 LFS158 Class Forum
- LFS158-JP クラス フォーラム
- 11 LFS162 Class Forum
- 2 LFS166 Class Forum
- 7 LFS167 Class Forum
- 3 LFS170 Class Forum
- 2 LFS171 Class Forum
- 3 LFS178 Class Forum
- 3 LFS180 Class Forum
- 2 LFS182 Class Forum
- 5 LFS183 Class Forum
- 33 LFS200 Class Forum
- 737 LFS201 Class Forum - Discontinued
- 3 LFS201-JP クラス フォーラム - Discontinued
- 20 LFS203 Class Forum
- 135 LFS207 Class Forum
- 2 LFS207-DE-Klassenforum
- 2 LFS207-JP クラス フォーラム
- 302 LFS211 Class Forum
- 56 LFS216 Class Forum
- 53 LFS241 Class Forum
- 50 LFS242 Class Forum
- 38 LFS243 Class Forum
- 16 LFS244 Class Forum
- 5 LFS245 Class Forum
- LFS246 Class Forum
- LFS248 Class Forum
- 93 LFS250 Class Forum
- 2 LFS250-JP クラス フォーラム
- 1 LFS251 Class Forum
- 156 LFS253 Class Forum
- 1 LFS254 Class Forum
- 2 LFS255 Class Forum
- 12 LFS256 Class Forum
- 1 LFS257 Class Forum
- 1.3K LFS258 Class Forum
- 11 LFS258-JP クラス フォーラム
- 135 LFS260 Class Forum
- 162 LFS261 Class Forum
- 43 LFS262 Class Forum
- 82 LFS263 Class Forum - Discontinued
- 15 LFS264 Class Forum - Discontinued
- 11 LFS266 Class Forum - Discontinued
- 24 LFS267 Class Forum
- 25 LFS268 Class Forum
- 37 LFS269 Class Forum
- 7 LFS270 Class Forum
- 202 LFS272 Class Forum - Discontinued
- 2 LFS272-JP クラス フォーラム
- 4 LFS147 Class Forum
- 2 LFS274 Class Forum
- 4 LFS281 Class Forum
- 17 LFW111 Class Forum
- 262 LFW211 Class Forum
- 185 LFW212 Class Forum
- 15 SKF100 Class Forum
- 1 SKF200 Class Forum
- 2 SKF201 Class Forum
- 797 Hardware
- 199 Drivers
- 68 I/O Devices
- 37 Monitors
- 104 Multimedia
- 174 Networking
- 91 Printers & Scanners
- 85 Storage
- 761 Linux Distributions
- 82 Debian
- 67 Fedora
- 17 Linux Mint
- 13 Mageia
- 23 openSUSE
- 149 Red Hat Enterprise
- 31 Slackware
- 13 SUSE Enterprise
- 355 Ubuntu
- 470 Linux System Administration
- 39 Cloud Computing
- 71 Command Line/Scripting
- Github systems admin projects
- 95 Linux Security
- 78 Network Management
- 102 System Management
- 47 Web Management
- 69 Mobile Computing
- 18 Android
- 38 Development
- 1.2K New to Linux
- 1K Getting Started with Linux
- 379 Off Topic
- 115 Introductions
- 177 Small Talk
- 26 Study Material
- 808 Programming and Development
- 304 Kernel Development
- 486 Software Development
- 1.8K Software
- 263 Applications
- 183 Command Line
- 3 Compiling/Installing
- 988 Games
- 317 Installation
- 103 All In Program
- 103 All In Forum
Upcoming Training
-
August 20, 2018
Kubernetes Administration (LFS458)
-
August 20, 2018
Linux System Administration (LFS301)
-
August 27, 2018
Open Source Virtualization (LFS462)
-
August 27, 2018
Linux Kernel Debugging and Security (LFD440)