(LFS258) Lab 11.2: Was anyone successful in creating a Path based ingress? I failed to make it work.

Hi all, I've finished lab 11.2 successfully, and I understand that it illustrates name-based virtual hosting ingress. Then I referred to the documentation https://kubernetes.io/docs/concepts/services-networking/ingress/ and tried the Path based ingresses, but non worked for me. Am I missing something, please?
Here are my services:
ahmad@k8s-master:~$ kc get svc NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 7d1h myingress-ingress-nginx-controller LoadBalancer 10.107.16.253 <pending> 80:31213/TCP,443:32356/TCP 51m myingress-ingress-nginx-controller-admission ClusterIP 10.106.108.230 <none> 443/TCP 51m web-one ClusterIP 10.100.215.198 <none> 80/TCP 54m web-two ClusterIP 10.101.173.35 <none> 80/TCP 56m ahmad@k8s-master:~$ curl 10.100.215.198 ... <body> <h1>Welcome to Web One!</h1> ... ahmad@k8s-master:~$ curl 10.101.173.35 ... <h1>Welcome to Web Two!</h1> ... ahmad@k8s-master:~$
Here is my ingress (first rule has a specific host with specific path | second rule has only a specific host):
ahmad@k8s-master:~$ kc get ingress ingress-test -o yaml apiVersion: networking.k8s.io/v1 kind: Ingress metadata: annotations: kubernetes.io/ingress.class: nginx creationTimestamp: "2022-08-13T22:19:51Z" generation: 5 name: ingress-test namespace: default resourceVersion: "44392" uid: d055dd79-1da7-44bf-bcd0-6058a5955452 spec: rules: - host: www.k8s-worker.com http: paths: - backend: service: name: web-two port: number: 80 path: /web-two pathType: ImplementationSpecific - host: www.k8s-master.com http: paths: - backend: service: name: web-one port: number: 80 path: / pathType: ImplementationSpecific status: loadBalancer: {}
Testing the second rule to service web-one is successfull:
ahmad@k8s-master:~$ curl -H "Host: www.k8s-master.com" http://10.107.16.253 ... <h1>Welcome to Web One!</h1> ...
Testing the first rule to service web-two fails (I am not sure how to specify the path in the curl command, I searched a lot and couldn't find a working solution):
ahmad@k8s-master:~$ curl -H "Host: www.k8s-worker.com" http://10.107.16.253/web-two <html> <head><title>404 Not Found</title></head> <body> <center><h1>404 Not Found</h1></center> <hr><center>nginx/1.23.1</center> </body> </html>
Best Answer
-
@a.zoubi It is correct behaviour because nothings lives inside nginx on non-root path, that's why page was not found. Seems in kubernetes doc it was not mentioned, may be because they believe it is obvious) I found another explanation for you in this article https://docs.giantswarm.io/advanced/ingress/configuration/
This is quote from it:
Note: Your applications need to be capable of running on a non-root path either by default or by setting the base path in their configuration.
1
Answers
-
Thanks for the answer @oleksazhel , yes it now makes sense.
I think I misunderstood the whole concept when I saw the graph in https://kubernetes.io/docs/concepts/services-networking/ingress/#simple-fanout , I thought that based on the path in the url, ingress will redirect the request to a new service to the Root Dir of that service. What you are saying, and what makes sense, is that the request will be redirected to a new service and the path will be forwarded to the service as well.1 -
Hi @a.zoubi,
I noticed in both cases, the Kubernetes documentation and the article referenced, the
pathType
is set toPrefix
for multiple hosts. The lab guide uses theImplementationSpecific
pathType
which may not be suited for this use case.Could you change the
pathType
values and test again?Regards,
-Chris1 -
@chrispokorni said:
Hi @a.zoubi,I noticed in both cases, the Kubernetes documentation and the article referenced, the
pathType
is set toPrefix
for multiple hosts. The lab guide uses theImplementationSpecific
pathType
which may not be suited for this use case.Could you change the
pathType
values and test again?Regards,
-ChrisThanks for the reply. Yes here is the result.
ahmad@k8s-master:~$ kc delete ingress ingress-test ahmad@k8s-master:~$ kc create -f ingress.yaml ahmad@k8s-master:~$ kc get ingress ingress-test -o yaml apiVersion: networking.k8s.io/v1 kind: Ingress metadata: ... spec: rules: - host: www.k8s-worker.com http: paths: - backend: service: name: web-two port: number: 80 path: /web-two pathType: Prefix - host: www.k8s-master.com http: paths: - backend: service: name: web-one port: number: 80 path: /web-one pathType: Prefix ... ahmad@k8s-master:~$ curl -H "Host: www.k8s-master.com" http://10.107.16.253/web-one ... <center><h1>404 Not Found</h1></center> <hr><center>nginx/1.23.1</center> ... ahmad@k8s-master:~$ curl -H "Host: www.k8s-master.com" http://10.107.16.253/web-two ... <center><h1>404 Not Found</h1></center> <hr><center>nginx</center> ...
Is the curl request correct? Or shall I send it in another way?
0 -
The answer by @oleksazhel is correct. I created two new nginx pods and created files in the web RootDirectory to serve new paths, and the ingress now works well.
The ingress created as above, and below are the test results.
ahmad@k8s-master:~$ kc get svc NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 9d myingress-ingress-nginx-controller LoadBalancer 10.107.16.253 <pending> 80:31213/TCP,443:32356/TCP 2d1h myingress-ingress-nginx-controller-admission ClusterIP 10.106.108.230 <none> 443/TCP 2d1h web-one ClusterIP 10.106.167.151 <none> 80/TCP 6m11s web-two ClusterIP 10.105.17.0 <none> 80/TCP 6m9s
Now curl to specific service requesting the path:
ahmad@k8s-master:~$ curl 10.106.167.151/web-one Hello, this is WEB ONE! ahmad@k8s-master:~$ curl 10.105.17.0/web-two Hello, this is WEB TWO!
Now curl to the ingress service ip adding host header and requesting the path:
ahmad@k8s-master:~$ curl -H "Host: www.k8s-master.com" 10.107.16.253/web-one Hello, this is WEB ONE! ahmad@k8s-master:~$ curl -H "Host: www.k8s-worker.com" 10.107.16.253/web-two Hello, this is WEB TWO! ahmad@k8s-master:~$
And it worked with pathType set to "Exact", "Prefix" or "ImplementationSpecific". It doesn't matter.
Also, you can remove the following line(s) from the ingress yaml file to make the rule based off of paths only:
... - host: www.k8s-worker.com ... - host: www.k8s-master.com ...
1
Categories
- All Categories
- 50 LFX Mentorship
- 103 LFX Mentorship: Linux Kernel
- 576 Linux Foundation IT Professional Programs
- 304 Cloud Engineer IT Professional Program
- 125 Advanced Cloud Engineer IT Professional Program
- 53 DevOps Engineer IT Professional Program
- 61 Cloud Native Developer IT Professional Program
- 5 Express Training Courses
- 5 Express Courses - Discussion Forum
- 2K Training Courses
- 19 LFC110 Class Forum
- 7 LFC131 Class Forum
- 27 LFD102 Class Forum
- 157 LFD103 Class Forum
- 20 LFD121 Class Forum
- 1 LFD137 Class Forum
- 61 LFD201 Class Forum
- 1 LFD210 Class Forum
- LFD210-CN Class Forum
- 1 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum
- LFD237 Class Forum
- 23 LFD254 Class Forum
- 611 LFD259 Class Forum
- 105 LFD272 Class Forum
- 1 LFD272-JP クラス フォーラム
- 1 LFD273 Class Forum
- 2 LFS145 Class Forum
- 24 LFS200 Class Forum
- 739 LFS201 Class Forum
- 1 LFS201-JP クラス フォーラム
- 11 LFS203 Class Forum
- 75 LFS207 Class Forum
- 300 LFS211 Class Forum
- 54 LFS216 Class Forum
- 47 LFS241 Class Forum
- 41 LFS242 Class Forum
- 37 LFS243 Class Forum
- 11 LFS244 Class Forum
- 36 LFS250 Class Forum
- 1 LFS250-JP クラス フォーラム
- LFS251 Class Forum
- 140 LFS253 Class Forum
- LFS254 Class Forum
- 1.1K LFS258 Class Forum
- 10 LFS258-JP クラス フォーラム
- 93 LFS260 Class Forum
- 132 LFS261 Class Forum
- 33 LFS262 Class Forum
- 80 LFS263 Class Forum
- 15 LFS264 Class Forum
- 11 LFS266 Class Forum
- 18 LFS267 Class Forum
- 17 LFS268 Class Forum
- 23 LFS269 Class Forum
- 203 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- LFS274 Class Forum
- LFS281 Class Forum
- 234 LFW211 Class Forum
- 172 LFW212 Class Forum
- 7 SKF100 Class Forum
- SKF200 Class Forum
- 902 Hardware
- 219 Drivers
- 74 I/O Devices
- 44 Monitors
- 115 Multimedia
- 209 Networking
- 101 Printers & Scanners
- 85 Storage
- 763 Linux Distributions
- 88 Debian
- 66 Fedora
- 15 Linux Mint
- 13 Mageia
- 24 openSUSE
- 142 Red Hat Enterprise
- 33 Slackware
- 13 SUSE Enterprise
- 357 Ubuntu
- 479 Linux System Administration
- 41 Cloud Computing
- 70 Command Line/Scripting
- Github systems admin projects
- 95 Linux Security
- 78 Network Management
- 108 System Management
- 49 Web Management
- 68 Mobile Computing
- 23 Android
- 30 Development
- 1.2K New to Linux
- 1.1K Getting Started with Linux
- 537 Off Topic
- 131 Introductions
- 217 Small Talk
- 21 Study Material
- 826 Programming and Development
- 278 Kernel Development
- 514 Software Development
- 928 Software
- 260 Applications
- 184 Command Line
- 3 Compiling/Installing
- 76 Games
- 316 Installation
- 62 All In Program
- 62 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)