When you create or deploy an application in a Container Service Kubernetes cluster, you can modify the scheduling rules of application instances as needed and deploy the instances to as many nodes and zones as possible to enhance application availability.

Configure scheduling rules when you create an application

  1. Log on to the EDAS console.
  2. In the left-side navigation pane, click Applications. In the top navigation bar, select a region. On the Applications page, select a namespace in the upper part and click Create Application in the upper-left corner.
  3. In the Basic Information step, set Cluster Type and Application Runtime Environment, and click Next.
    Parameter Description
    Cluster Type Select Kubernetes Clusters.
    Application Runtime Environment Select an application runtime environment based on the type of the hosted application.
    • Java:
      • Custom: Select this option if you want to use a custom image to deploy the application to a Kubernetes cluster.
      • Java: Select this option if you want to use a universal JAR package to deploy the application as a Dubbo or a Spring Boot application. You can specify the Java Environment parameter after you select this option.
      • Tomcat: Select this option if you want to use a universal WAR package to deploy the application as a Dubbo or a Spring application. You can specify the Java Environment and Container Version parameters after you select this option.
      • EDAS-Container (HSF): Select this option if you want to use a WAR or FatJar package to deploy the application as a High-Speed Service Framework (HSF) application. You can specify the Java Environment, Pandora Version, and Ali-Tomcat Version parameters after you select this option.
    • PHP: Select this option if you want to run PHP applications on Apache HTTP Server.
    • Node.js, C++, Go, and Other Languages: Select this option if you want to run a microservice application that is developed in a random language and deployed by using a custom image.
  4. In the Configurations step, configure the environment information, basic information, deployment method, and resource parameters for the application, and click Next.
  5. In the Advanced Settings step, click Scheduling Rules and configure the rules as needed.
    Parameter Description
    Zone Scheduling
    • Default Scheduling: By default, the instances are scheduled based on the status of cluster resources. The system may deploy all instances to the same zone. Therefore, this scheduling rule does not ensure high availability.
    • Deploy in As Many Zones As Possible: Anti-affinity rules are used to deploy the instances to as many zones as possible to ensure high availability.
    Node Scheduling
    • Default Scheduling: By default, the instances are scheduled based on the loads of cluster nodes.
    • Deploy to as Many Nodes as Possible: The instances of one application are deployed to as many nodes as possible to ensure high availability of the application.
  6. Click Create Application.
  7. In the Creation Completed step, confirm the settings in Basic Information, Configurations, and Advanced Settings, and click Create Application.
    In the upper part of the Application Overview page, click View Details. On the Change List page, you can view the change process. Wait a few minutes until the application is deployed. After the change process is complete, view the running status of the instances in the Basic Information section of the Application Overview page. If the pod that runs the application is in the running state, the application is deployed.

Configure scheduling rules when you update an application

You can configure scheduling rules when you create an application, or configure or update scheduling rules when you deploy an application.

  1. Log on to the EDAS console.
  2. In the left-side navigation pane, click Applications. In the top navigation bar, select a region. On the Applications page, select a namespace in the upper part, and select Container Service or Serverless Kubernetes Cluster from the Cluster Type drop-down list. Then, find the application that you want to deploy, and click the application name.
  3. On the Application Overview or Basic Information page, choose Deploy > Deploy in the upper-right corner.
  4. On the Select Deployment Mode page, select a deployment mode and click Start Deployment in the upper-right corner of the specified deployment mode section.
  5. Set the environment and deployment package information, click Scheduling Rules, complete the configuration as needed, and then click OK.
    Parameter Description
    Zone Scheduling
    • Default Scheduling: By default, the instances are scheduled based on the status of cluster resources. The system may deploy all instances to the same zone. Therefore, this scheduling rule does not ensure high availability.
    • Deploy in As Many Zones As Possible: Anti-affinity rules are used to deploy the instances to as many zones as possible to ensure high availability.
    Node Scheduling
    • Default Scheduling: By default, the instances are scheduled based on the loads of cluster nodes.
    • Deploy to as Many Nodes as Possible: The instances of one application are deployed to as many nodes as possible to ensure high availability of the application.
    Notice The application is restarted after you click OK. We recommend that you perform this operation during off-peak hours.