In Enterprise Distributed Application Service (EDAS), an Ingress is a collection of routing rules that are used to route external HTTP or HTTPS traffic to internal Services. You can configure different Kubernetes Ingresses for an application. This way, external requests can be routed to different Services in a cluster based on different routing rules. This topic describes how to configure an Ingress for an application and configure routing rules in the EDAS console.
Prerequisites
Background information
By default, an Ingress controller is deployed when you create a Kubernetes cluster. The Ingress controller is used to parse the routing rules of the Ingresses in the cluster. After the Ingress controller receives a request that matches a routing rule of an Ingress, the Ingress controller routes the request to the corresponding Service. Then, the Service forwards the request to pods and the pods process the request.
- A Service is an abstraction of an application that is deployed on a set of replicated pods.
- An Ingress is a collection of routing rules that are used to route external HTTP or HTTPS traffic to internal Services.
- An Ingress controller is a reverse proxy that parses the routing rules of Ingresses and routes HTTP or HTTPS traffic to the corresponding Service based on the rules.
Constraint on managing Ingresses in a Kubernetes cluster
You must not modify the Ingress resources created by EDAS. The resources have the
edas-domain: edas-admin
or edas-domain
tag.
Procedure
Verify the result
In the address bar of a browser, enter the domain name and the path that are specified in the routing rule. Use the Domain name/Path format. Check whether you can access the specified Service.