Enterprise Distributed Application Service:Deploy an application to a Kubernetes cluster from IntelliJ IDEA

Step 1: Install Alibaba Cloud Toolkit

1. Open IntelliJ IDEA.

2. Open the plug-in settings:

   • macOS: Choose IntelliJ IDEA > Preferences > Plugins.

   • Windows: Choose File > Settings > Plugins.

3. In the search box, enter Alibaba Cloud Toolkit and click the search icon.

4. Click Install.

   

   

5. Restart IntelliJ IDEA. After the restart, the Alibaba Cloud Toolkit icon appears in the toolbar.

If you already have the plug-in installed, upgrade it to the latest version through the same Plugins settings page.

Step 2: Configure your Alibaba Cloud account

Set up your AccessKey pair so the plug-in can access EDAS on your behalf.

1. In IntelliJ IDEA, choose Tools > Alibaba Cloud > Preferences.

2. In the left navigation pane, choose Alibaba Cloud Toolkit > Accounts.

3. Enter your Access Key ID and Access Key Secret, then click OK.

   

Get your AccessKey pair:

• If you have an Alibaba Cloud account, click Get existing AK/SK on the Accounts page. Log in and retrieve your AccessKey ID and AccessKey secret from the AccessKey Management page.

• If you do not have an account, click Sign up to create one, then retrieve your AccessKey pair.

If your EDAS service runs on Apsara Stack Enterprise, configure an endpoint before proceeding. See Configure an endpoint for Apsara Stack Enterprise.

Step 3: Deploy your application

1. In IntelliJ IDEA, choose Tools > Alibaba Cloud > Deploy to EDAS > EDAS for Kubernetes Application. Alternatively, choose Run > Edit Configurations. In the Run/Debug configurations dialog box, choose Templates > EDAS on Alibaba Cloud > EDAS for Kubernetes Application.

2. On the Settings tab of the Deploy to EDAS dialog box, set the following parameters:

   Important

   If the application does not appear in the list, see Authorize a RAM user for EDAS.

   Parameter	Description
   Region	The region where the application is deployed.
   Namespace	The microservices namespace where the application is deployed.
   Application	The name of the application.

   

3. Select a deployment method:

   Method	Description
   Maven Build	Adds a Maven build job to create the deployment package. For multi-module projects, see Deploy a multi-module project.
   Upload File	Uploads a WAR or JAR package for deployment.
   Build Image	Builds a container image from a Dockerfile. Set the Context Directory, Dockerfile path, and image Version.
   Select Image	Deploys from an existing container image selected from the Select Image drop-down list.

   

4. (Optional) Click the Advanced tab to configure additional deployment parameters. For full parameter details, see the DeployK8sApplication API reference.

   • Application Environment: Set the runtime environment. Specify a new PackageVersion each time you deploy.

   • Startup Command: Specify the command and arguments to run when the container starts.

   • Environments: Define environment variables for the application.

   • Persistence: Configure persistent storage volumes.

   • Storage: Configure local storage.

   • Application Management: Set lifecycle hooks and health probes:

     Setting	Description
     Poststart	A container lifecycle hook triggered after a container is created. If the handler fails, the container is stopped and the restart policy determines whether to restart it.
     PreStop	A container lifecycle hook triggered before a container is deleted. The handler runs before the delete request reaches the Docker daemon. The daemon sends a SIGTERM signal regardless of the handler result.
     Liveness	A health probe that checks application health. If unhealthy, Kubernetes deletes and re-creates the container.
     Readiness	A health probe that checks whether the application has started and is running as expected. If the application cannot run as expected, the container status is updated.

   

5. Click Apply, then click Run. Check the deployment log in the Console tab of IntelliJ IDEA to verify the result.

Deploy a multi-module project

For Maven multi-module projects, the last Maven job in the Before launch section must build the submodule you want to deploy.

Example: The CarShop project has the following structure:

carshop
├── itemcenter-api
├── itemcenter
├── detail

Both itemcenter and detail depend on itemcenter-api. To deploy the itemcenter submodule, add these two Maven jobs to the Before launch section:

1. Run mvn clean install in the parent project CarShop.

2. Run mvn clean package in the itemcenter submodule.

Manage Maven build jobs

In the Deploy to EDAS dialog box, the Before launch section lets you create, delete, modify, and reorder Maven build jobs.

In the Select Maven Goal dialog box, click the folder icon next to the Working directory field to select a module, then enter the build command in the Command line field.

Authorize a RAM user for EDAS

If a RAM user cannot see applications in the deployment list, the user is either not synchronized to EDAS or lacks the required permissions. Choose one of the following approaches to grant access.

Configure an endpoint for Apsara Stack Enterprise

If your EDAS service runs on Apsara Stack Enterprise, configure an endpoint in Alibaba Cloud Toolkit before deploying. Contact EDAS technical support to get the endpoint value.

1. In the Preference (Filtered) dialog box, choose Appearance & Behavior > Endpoint.

2. Enter the endpoint value and click Apply and Close.