Use an Apsara Devops pipeline to deploy an application to SAE with a Kubernetes YAML file

1. Upload the source code

To quickly try this procedure, upload the sample code spring-boot-demo.zip to a source code repository, such as a self-managed GitLab, Codeup, or GitHub.

The files in the sample code are described as follows:

• Dockerfile: Builds an image from the source code.

• manifests/dp.yaml: Specifies the configuration for deploying the application to SAE using a Kubernetes YAML file.

2. Configure the Apsara Devops pipeline

Log in to the Apsara Devops pipeline console and click New Pipeline.

This topic demonstrates the procedure for creating a pipeline from an empty template. Select Empty Template and click Create.

2. 1 Set the code source

On the Flow Configuration page, click Add Pipeline Source. Select the source code repository type for the sample code. Then, configure the Code Repository and Default Branch.

If this is the first time you are using the pipeline, you must click Add Service Connection or Enterprise Public Key to grant the Apsara Devops pipeline access to your source code repository.

2. 2 Build and upload the image

In the next stage of the pipeline, add a task to build and upload the image:

1. Click the default Empty Task node. On the Edit page, configure the following parameters:

   • Set Build Cluster to Apsara Devops China (Hong Kong) Build Cluster because the Dockerfile in the sample code depends on images from outside China.

   • Select a Build Node. The node must be Linux/amd64.

2. Click Add Step, and then select Build Image And Push To ACR (Personal Edition) or Build Image And Push To ACR (Enterprise Edition) from the Build category.

   This topic assumes that you have activated Container Registry (ACR) and have created a Personal Edition instance or created an Enterprise Edition instance.

   Build and push image to ACR (Personal Edition)

   The first time you use the pipeline, you must click Add Service Connection to grant the Apsara DevOps pipeline access to Container Registry.

   Configure the following parameters:

   • Select the destination Region and Repository to upload the image.

   • Set the Tag to a fixed parameter, such as 1.0, or a dynamic parameter, such as ${DATETIME}. The dynamic parameter uses the current date and time as the version name when the image is pushed to ACR.

   • Set the Dockerfile Path to Dockerfile because the Dockerfile file in the sample code is in the root directory of the code repository.

   

   Build and push image to ACR (Enterprise Edition)

   Important

   The destination ACR Enterprise Edition instance must have Internet access enabled for the image repository. You must then add the public egress IP address of the Flow build cluster to the public network whitelist of ACR. For more information, see Configure public network access control. To find the public egress IP address of the Flow build cluster, see Build cluster.

   The first time you use the pipeline, you must click Add Service Connection to grant the Apsara DevOps pipeline access to Container Registry.

   Configure the following parameters:

   • Select the destination Region, Enterprise Instance, Namespace, and Repository to upload the image.

   • Set the Tag. You can use a fixed parameter, such as 1.0, or a dynamic parameter, such as ${DATETIME}. The dynamic parameter uses the current date and time as the tag when the image is pushed to ACR.

   • Set the Dockerfile Path to Dockerfile because the Dockerfile file is in the root directory of the code repository.

   

2. 3 Deploy the SAE application

In the next stage of the pipeline, add a task to deploy the SAE application:

1. To create a task, click New Task and select the Blank Task template. On the Edit page, configure the following parameters:

   • Select a Build Node. Only Linux/amd64 build nodes are supported.

2. Click Add Step, and then in the Publish category, select Kubectl SAE Publish.

   The first time you use the pipeline, you must click Add Service Connection to grant the Apsara DevOps pipeline access to SAE.

   Configure the following parameters:

   • Select the Region and Namespace where the destination SAE application is located. In this example, Namespace is set to default.

   • Set the YAML Path to manifests because the YAML file in the sample code is in the manifests directory of the code repository.

   • Set the Variables. Add a definition for the IMAGE variable, which is referenced in the sample YAML file: IMAGE = Build and push image to ACR (Personal/Enterprise Edition).Image Public Address. The variable is automatically replaced when the application is deployed.

   

3. Run the Apsara Devops pipeline and verify the result

1. Save and run the pipeline.

2. After the run completes, click Logs on each node to view the execution process and results. The logs for the SAE application deployment node include all scanned YAML files, the standard Kubernetes deployment output, and a resource summary.

   

3. Log on to the SAE console. In the navigation pane on the left, choose Application Management > Application List. Then, select the destination region and namespace. You can view the deployed application. The application name is test-deployment.

4. Clean up resources

Click the deployed application. On the Basic Information page, choose More > Delete Application. Follow the on-screen instructions to delete the application.