Enterprise Distributed Application Service (EDAS) will be updated on the Alibaba Cloud International site (alibabacloud.com) from 20:00 to 24:00 on May 26, 2022, UTC+8. During the update, you can normally use the EDAS console, and existing applications normally run. Feel free to use EDAS.
- Cross-cluster application management: This feature allows you to manage the lifecycle of applications that are deployed across multiple Container Service for Kubernetes (ACK) clusters in EDAS. When you use an application template to deploy applications across clusters, you can use custom configurations for the application in a specific cluster based on the configurations defined in the template. This way, you can enjoy a flexible configuration mode. In addition, you can release applications in single-phase or multi-phase mode and query change logs after applications are released. For more information, see Manage multi-cluster applications.
- Application template management: You can use an application template to apply the same application configurations to multiple applications across Kubernetes clusters. This allows you to implement cross-cluster application release and management and continuous application O&M. For more information, see Manage application templates.
- Application import and export: EDAS allows you to import, export, and clone one or more applications at a time across different EDAS environments or Alibaba Cloud accounts. For more information, see Import applications, Export applications, and Clone an application.
- Support for Application Load Balancer (ALB) Ingresses: EDAS allows you to configure ALB Ingresses, which are based on Alibaba Cloud ALB instances, for your applications. ALB Ingresses provide improved traffic routing capabilities, such as complex routing and automatic certificate discovery. ALB Ingresses also support auto scaling and are fully managed by Alibaba Cloud. For more information, see Select an Ingress type and Create an ALB Ingress for an application.
- Enhanced integration with native Kubernetes: EDAS allows you to configure labels and annotations when you deploy an application, use a Service of the NodePort type to expose an application, and set the externalTrafficPolicy parameter when you associate a Server Load Balancer (SLB) instance with an application. For more information, see Add labels to application pods and Configure annotations.
- Graceful start of applications: When you release or deploy an application, you can implement graceful start without traffic loss by using methods such as delayed service registration and service prefetching. For more information, see Configure microservices governance.
- Microservices Engine (MSE) Nacos instances as registries: EDAS integrates with MSE. When you create a microservices namespace, you can associate an MSE Nacos instance with the microservices namespace. Then, you can register the applications that you release in this microservices namespace with the MSE Nacos instance. An MSE Nacos instance can serve as a registry and provides higher performance and stability than the shared registry of EDAS. For more information, see the Manage microservices namespaces in the EDAS console topic for Kubernetes clusters and the Manage microservices namespaces in the EDAS console topic for Elastic Compute Service (ECS) clusters.
- Support for custom OpenJDK versions: When you deploy an application in an ECS cluster, you can specify an installation command to use a custom OpenJDK version. When the application starts, the command is run to install OpenJDK of the custom version. For more information, see Create and deploy an application in an ECS cluster.
- Auto scaling-related configuration customization for Kubernetes clusters: If the version of your Kubernetes cluster is later than 1.18, you can customize specific scaling configurations, such as the cooldown time and step size, when you set auto scaling policies for applications that are deployed in the cluster. For more information, see Auto scaling.
- Support for Kubernetes clusters V1.22: EDAS allows you to import Kubernetes clusters of version 1.22.