Enterprise Distributed Application Service (EDAS) allows you to use Kubernetes clusters deployed on Alibaba Cloud to manage containerized applications. You can also use Kubernetes clusters deployed on third-party clouds and self-managed Kubernetes clusters deployed in data centers to manage containerized applications. If you need to isolate application runtime environments for security purposes, you can create and use namespaces to isolate resources and services.

Namespaces

Namespaces provide applications with isolated runtime environments, such as the development, testing, and production environments. You can use namespaces to isolate resources and services.

By default, EDAS provides a default namespace. EDAS also allows you to create namespaces.

Manage external clusters

EDAS allows you to use Kubernetes clusters deployed on Alibaba Cloud to manage containerized applications. You can also use Kubernetes clusters deployed on third-party clouds and self-managed Kubernetes clusters deployed in data centers to manage containerized applications. You need only to import Kubernetes clusters to the EDAS console so that you can host applications to the Kubernetes clusters. No other complicated operations are required.

EDAS does not provide an entrance for creating Kubernetes clusters. You must go to the Container Service for Kubernetes (ACK) console to create Kubernetes clusters deployed on Alibaba Cloud or register Kubernetes clusters deployed on third-party clouds and self-managed Kubernetes clusters deployed in data centers. ACK provides a stable and high-performance container network by deeply integrating with the networks of Kubernetes clusters and virtual private clouds (VPCs) of Alibaba Cloud. Different VPCs are logically isolated.

  • Kubernetes clusters deployed on Alibaba Cloud

    EDAS is seamlessly connected to Container Service for Kubernetes (ACK). Therefore, EDAS allows you to import dedicated Kubernetes clusters, managed Kubernetes clusters, and serverless Kubernetes clusters that are created in the Container Service for Kubernetes (ACK) console. For details about the comparison of the three forms of clusters, see What is Container Service for Kubernetes?.

    Dedicated Kubernetes clusters and managed Kubernetes clusters that are imported to EDAS correspond to Container Service Kubernetes clusters in EDAS. Serverless Kubernetes clusters that are imported to EDAS correspond to serverless Kubernetes clusters in EDAS.

  • Kubernetes clusters deployed on third-party clouds and self-managed Kubernetes clusters deployed in data centers

    During routine operations and maintenance (O&M), you may need to manage Kubernetes clusters that are deployed on Alibaba Cloud and in data centers. You may also need to manage Kubernetes clusters that are deployed on the clouds of different service providers. In this case, you can register these clusters with the Container Service for Kubernetes (ACK) console to implement capabilities, such as unified security governance, application management and monitoring, and logging. This reduces O&M costs.

    For more information about how to register external clusters with the ACK console, see Create a cluster registration proxy and register an on-premises cluster.

    If Kubernetes clusters deployed on third-party clouds and self-managed Kubernetes clusters deployed in data centers are imported to EDAS, these Kubernetes clusters correspond to Container Service Kubernetes clusters in EDAS.

Note The principle of hosting applications to Kubernetes clusters deployed on Alibaba Cloud or Kubernetes clusters deployed on third-party clouds and self-managed Kubernetes clusters deployed in data centers is similar. Applications are hosted to a pod or a group of pods.