When applications are hosted in Kubernetes clusters in Enterprise Distributed Application Service (EDAS), these applications cannot be directly accessed by other applications. This topic describes different methods that you can use to access applications.

Application access methods

The following table describes the methods that you can use to access applications in Kubernetes clusters in EDAS.
Application access method Description References
Access over the Internet

You can bind an Internet-facing Server Load Balancer (SLB) instance to a Service of the LoadBalancer type so that you can use the public IP address of the SLB instance to directly access backend pods.

Access over a virtual private cloud (VPC)

You can bind an internal-facing SLB instance in a VPC to a Service of the LoadBalancer type so that you can use the private IP address of the SLB instance to directly access backend pods.

Internal access in a cluster

You can add a Service of the ClusterIP type. The system automatically generates a fixed IP address (ClusterIP) for the Service.

You can access the IP address of the Service in the cluster. The Service forwards access traffic to backend pods and implements load balancing for the pods.

Add a service
Access based on the routing rules of Ingresses

You can create one or more Kubernetes Ingresses for a Service.

When the Ingress controller receives an external HTTP request for access to backend Services, the Ingress controller parses the routing rules of the Ingresses and routes the HTTP traffic to the corresponding Service based on the rules.

Create a Kubernetes ingress for an application