You must configure environment variables to run an application in the system. For example, the commands of a Java application can be run only after the JAVA_HOME and PATH environment variables are configured. This topic describes how to configure environment variables for applications in the Enterprise Distributed Application Service (EDAS) console.

Background information

The EDAS console allows you to configure the following three types of environment variables:
  • Custom environment variables: the environment variables that you customize when you create an application.
  • ConfigMaps: the predefined configurations that do not need to be kept confidential. If you want to apply a ConfigMap to an application, the application must be in the same region, cluster, and Kubernetes namespace as the ConfigMap. Otherwise, the application cannot use the ConfigMap.

    For more information about how to create a ConfigMap, see Create a ConfigMap.

  • Secrets: the predefined configurations, such as passwords and certificates, that need to be kept confidential. If you want to apply a secret to an application, the application must be in the same region, cluster, and Kubernetes namespace as the secret. Otherwise, the application cannot use the secret.

    For more information about how to create a secret, see Create a secret.

Configure environment variables 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, specify 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 in 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 this application as a PHP application on Apache HTTP Server.
    • Node.js, C ++, Go, and Other Languages: Select this option if you want to use a custom image to deploy the application in a Kubernetes cluster. The configuration process for multi-language applications is not described in this topic. For more information, see Use images to deploy microservice-based multi-language in Kubernetes clusters.
  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 Environment Variables and configure environment variables as needed.
    When you create the application, pass the environment variables that you configure to the container to be generated. This way, you do not need to repeatedly add commonly used environment variables. EDAS allows you to customize environment variables and configure environment variables by using ConfigMaps and secrets. Select a method as needed.
    • Customize environment variables.
      • If you want to specify parameters for the Java virtual machine (JVM) heap memory, JVM properties, and Java agent, add the parameters in this step:
        • Variable Name: CATALINA_OPTS
        • Variable Value: [Parameter to be added] $(EDAS_CATALINA_OPTS)
        Custom - Environment variable 1
      • If you are using a MySQL image, you can configure the following environment variables:
        • MYSQL_ROOT_PASSWORD: required. Allows you to set a MySQL root password.
        • MYSQL_USER and MYSQL_PASSWORD: optional. Allow you to create an account in addition to the root account and set a password.
        • MYSQL_DATABASE: optional. Allows you to specify the database that you want to create when the container is generated.
      • If you are using another type of image, configure the environment variables as needed.
    • Use ConfigMaps to configure environment variables.

      Select a ConfigMap from the Variable Value/Variable Reference drop-down list. A ConfigMap may contain multiple key-value pairs. Select a key-value pair as needed.

      ConfigMap - Environment variable
    • Use secrets to configure environment variables.

      Select a secret from the Variable Value/Variable Reference drop-down list. A secret may contain multiple key-value pairs. Select a key-value pair as needed.

      Secret - Environment variable
  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 environment variables when you update an application

If you do not configure environment variables when you create an application, you can configure them when you deploy the 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 runtime environment and deployment package for the application, click Environment Variables, complete the configuration as needed, and then click OK.
    When you create the application, pass the environment variables that you configure to the container to be generated. This way, you do not need to repeatedly add commonly used environment variables. EDAS allows you to customize environment variables and configure environment variables by using ConfigMaps and secrets. Select a method as needed.
    • Customize environment variables.
      • If you want to specify parameters for the Java virtual machine (JVM) heap memory, JVM properties, and Java agent, add the parameters in this step:
        • Variable Name: CATALINA_OPTS
        • Variable Value: [Parameter to be added] $(EDAS_CATALINA_OPTS)
        Custom - Environment variable 1
      • If you are using a MySQL image, you can configure the following environment variables:
        • MYSQL_ROOT_PASSWORD: required. Allows you to set a MySQL root password.
        • MYSQL_USER and MYSQL_PASSWORD: optional. Allow you to create an account in addition to the root account and set a password.
        • MYSQL_DATABASE: optional. Allows you to specify the database that you want to create when the container is generated.
      • If you are using another type of image, configure the environment variables as needed.
    • Use ConfigMaps to configure environment variables.

      Select a ConfigMap from the Variable Value/Variable Reference drop-down list. A ConfigMap may contain multiple key-value pairs. Select a key-value pair as needed.

      ConfigMap - Environment variable
    • Use secrets to configure environment variables.

      Select a secret from the Variable Value/Variable Reference drop-down list. A secret may contain multiple key-value pairs. Select a key-value pair as needed.

      Secret - Environment variable
    Notice The application is restarted after you click OK. We recommend that you configure environment variables during off-peak hours.

Verify the result

  • Method 1

    In the left-side navigation pane of the application details page, click Change List to view the application change details. If the value in the Change Status column is Succeeded, the application is deployed and the configuration takes effect.

  • Method 2

    On the Application Overview page, click Running Pods (Click View) next to Running Status. In the Pod section of the panel that appears, check the Status column of the pod. If a green dot appears, the application is in the running state. This means that the application is deployed as expected and the configuration takes effect.