Welcome to the Linux Foundation Forum!

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

Posts: 4
edited August 2022 in LFS258 Class Forum

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:

  1. ahmad@k8s-master:~$ kc get svc
  2. NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
  3. kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 7d1h
  4. myingress-ingress-nginx-controller LoadBalancer 10.107.16.253 <pending> 80:31213/TCP,443:32356/TCP 51m
  5. myingress-ingress-nginx-controller-admission ClusterIP 10.106.108.230 <none> 443/TCP 51m
  6. web-one ClusterIP 10.100.215.198 <none> 80/TCP 54m
  7. web-two ClusterIP 10.101.173.35 <none> 80/TCP 56m
  8. ahmad@k8s-master:~$ curl 10.100.215.198
  9. ...
  10. <body>
  11. <h1>Welcome to Web One!</h1>
  12. ...
  13. ahmad@k8s-master:~$ curl 10.101.173.35
  14. ...
  15. <h1>Welcome to Web Two!</h1>
  16. ...
  17. ahmad@k8s-master:~$

Here is my ingress (first rule has a specific host with specific path | second rule has only a specific host):

  1. ahmad@k8s-master:~$ kc get ingress ingress-test -o yaml
  2. apiVersion: networking.k8s.io/v1
  3. kind: Ingress
  4. metadata:
  5. annotations:
  6. kubernetes.io/ingress.class: nginx
  7. creationTimestamp: "2022-08-13T22:19:51Z"
  8. generation: 5
  9. name: ingress-test
  10. namespace: default
  11. resourceVersion: "44392"
  12. uid: d055dd79-1da7-44bf-bcd0-6058a5955452
  13. spec:
  14. rules:
  15. - host: www.k8s-worker.com
  16. http:
  17. paths:
  18. - backend:
  19. service:
  20. name: web-two
  21. port:
  22. number: 80
  23. path: /web-two
  24. pathType: ImplementationSpecific
  25. - host: www.k8s-master.com
  26. http:
  27. paths:
  28. - backend:
  29. service:
  30. name: web-one
  31. port:
  32. number: 80
  33. path: /
  34. pathType: ImplementationSpecific
  35. status:
  36. loadBalancer: {}

Testing the second rule to service web-one is successfull:

  1. ahmad@k8s-master:~$ curl -H "Host: www.k8s-master.com" http://10.107.16.253
  2. ...
  3. <h1>Welcome to Web One!</h1>
  4. ...

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):

  1. ahmad@k8s-master:~$ curl -H "Host: www.k8s-worker.com" http://10.107.16.253/web-two
  2. <html>
  3. <head><title>404 Not Found</title></head>
  4. <body>
  5. <center><h1>404 Not Found</h1></center>
  6. <hr><center>nginx/1.23.1</center>
  7. </body>
  8. </html>
  9.  

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Best Answer

  • Posts: 57
    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:

    1. 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.

Answers

  • Posts: 4

    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.

  • Posts: 2,434

    Hi @a.zoubi,

    I noticed in both cases, the Kubernetes documentation and the article referenced, the pathType is set to Prefix for multiple hosts. The lab guide uses the ImplementationSpecific pathType which may not be suited for this use case.

    Could you change the pathType values and test again?

    Regards,
    -Chris

  • Posts: 4

    @chrispokorni said:
    Hi @a.zoubi,

    I noticed in both cases, the Kubernetes documentation and the article referenced, the pathType is set to Prefix for multiple hosts. The lab guide uses the ImplementationSpecific pathType which may not be suited for this use case.

    Could you change the pathType values and test again?

    Regards,
    -Chris

    Thanks for the reply. Yes here is the result.

    1. ahmad@k8s-master:~$ kc delete ingress ingress-test
    2.  
    3. ahmad@k8s-master:~$ kc create -f ingress.yaml
    4.  
    5. ahmad@k8s-master:~$ kc get ingress ingress-test -o yaml
    6. apiVersion: networking.k8s.io/v1
    7. kind: Ingress
    8. metadata:
    9. ...
    10. spec:
    11. rules:
    12. - host: www.k8s-worker.com
    13. http:
    14. paths:
    15. - backend:
    16. service:
    17. name: web-two
    18. port:
    19. number: 80
    20. path: /web-two
    21. pathType: Prefix
    22. - host: www.k8s-master.com
    23. http:
    24. paths:
    25. - backend:
    26. service:
    27. name: web-one
    28. port:
    29. number: 80
    30. path: /web-one
    31. pathType: Prefix
    32. ...
    33.  
    34. ahmad@k8s-master:~$ curl -H "Host: www.k8s-master.com" http://10.107.16.253/web-one
    35. ...
    36. <center><h1>404 Not Found</h1></center>
    37. <hr><center>nginx/1.23.1</center>
    38. ...
    39. ahmad@k8s-master:~$ curl -H "Host: www.k8s-master.com" http://10.107.16.253/web-two
    40. ...
    41. <center><h1>404 Not Found</h1></center>
    42. <hr><center>nginx</center>
    43. ...

    Is the curl request correct? Or shall I send it in another way?

  • Posts: 4
    edited August 2022

    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.

    1. ahmad@k8s-master:~$ kc get svc
    2. NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
    3. kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 9d
    4. myingress-ingress-nginx-controller LoadBalancer 10.107.16.253 <pending> 80:31213/TCP,443:32356/TCP 2d1h
    5. myingress-ingress-nginx-controller-admission ClusterIP 10.106.108.230 <none> 443/TCP 2d1h
    6. web-one ClusterIP 10.106.167.151 <none> 80/TCP 6m11s
    7. web-two ClusterIP 10.105.17.0 <none> 80/TCP 6m9s

    Now curl to specific service requesting the path:

    1. ahmad@k8s-master:~$ curl 10.106.167.151/web-one
    2. Hello, this is WEB ONE!
    3. ahmad@k8s-master:~$ curl 10.105.17.0/web-two
    4. Hello, this is WEB TWO!

    Now curl to the ingress service ip adding host header and requesting the path:

    1. ahmad@k8s-master:~$ curl -H "Host: www.k8s-master.com" 10.107.16.253/web-one
    2. Hello, this is WEB ONE!
    3. ahmad@k8s-master:~$ curl -H "Host: www.k8s-worker.com" 10.107.16.253/web-two
    4. Hello, this is WEB TWO!
    5. 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:

    1. ...
    2. - host: www.k8s-worker.com
    3. ...
    4. - host: www.k8s-master.com
    5. ...

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Welcome!

It looks like you're new here. Sign in or register to get started.
Sign In

Categories

Upcoming Training