This is the 7th day of my participation in the August More Text Challenge
Common ingress policies
(1) Forward the request to a single back-end service
Based on this setup, access requests from the client to the Ingress Controller are forwarded to a backend unique Service, in which case the Ingress does not have to define any rules. For example, the Ingress policy configuration on myWeb :8080 is as follows:
(2) Forward requests to different urls of the same domain name to different back-end services
This configuration is often used in scenarios where a web site provides different services through different paths. For example, /web refers to accessing a Web page, and/API refers to accessing an API interface, corresponding to the two services on the back end. For example, to forward the access request to mywebsite.com/web to web-service:80 and mywebsite.com/api to apI-service :80, configure the Ingress policy as follows:
This configuration is often used when a website provides different services using different domain names or virtual hostnames. For example, if the foo.bar.com domain name is served by Service1 and the bar.foo.com domain name is served by service2, all requests for foo.bar.com are forwarded to the service1:80 service. The Ingress policy configuration for forwarding bar.foo.com access requests to service2:80 is as follows:
(4) Forwarding rules without using domain names
This configuration is used when a website provides services without using a domain name. In this case, any Node running ingress-Controller can access the back-end services. For example, the Ingress policy configuration for forwarding access requests from/Demo to webApp :8080/ Demo is as follows: Note that when the Ingress forwarding rule without domain name is used, HTTPS is used by default. If you want to use an insecure HTTP, you need to adjust the configuration of the Ingress Controller, which is usually used in a secure network environment.
