What's New

1

Release management

Release tasks of different types provide functions for releasing applications: single-component release, batch operations (release, upgrade, and clone), and dependency-based orchestration. This feature enables you to flexibly deploy components in batches, improving service efficiency and user experience.

• Batch deployment release task: deploys components of different technology stacks in different deployment environments of different applications.
• Batch upgrade release task: upgrades components of different applications in batches and specifies the component upgrade sequence to ensure service running during the upgrade.
• Batch clone release task: clones components of different applications and quickly configures and deploys components in batches.

Open beta testing

Release Management

2

Plug-in management

Sermant Agent can be automatically mounted to Spring Cloud application components deployed in container mode through the Sermant Injector plug-in. Sermant Agent then can be used to access ServiceComb engines with security authentication disabled without modifying code. After that, engine functions such as application registration and discovery, full-link dark launch, graceful startup and shutdown, and labeled routing can be used.

Commercial use

Installing Sermant Injector

3

Multi-container deployment

If a container-based component is deployed from an image package, multi-container deployment is supported. This deployment mode can be used to build complex application systems where different services or components are packaged in different containers.

Commercial use

Creating and Deploying a Component Based on a Container Using UI Configurations

4

Tolerance policies for component instances

For container-deployed components, tolerations allow the scheduler to schedule pods to nodes with target taints. Tolerations work with node taints. Each node allows one or more taints. If no tolerance is configured for a pod, the scheduler will schedule the pod based on node taint policies to prevent the pod from being scheduled to an inappropriate node.

Commercial use

Configuring a Tolerance Policy of a Component Instance

1

Access dependent services through VPC endpoints when building images

VPC Endpoint is a cloud service that provides secure and private channels to connect your VPCs to VPC endpoint services. It allows you to plan networks flexibly without having to use EIPs.
When building images for components in the Kubernetes environment, you can create VPC endpoints to communicate with Object Storage Service (OBS) and SoftWare Repository for Container (SWR), and use API Gateway (APIG) to call functional APIs of ServiceStage based on configured private domain names.

Commercial use

How Can I Access Dependent Services Through VPC Endpoints When Building Images?

2

Access dependent services through VPC endpoints when installing VM agents

VPC Endpoint is a cloud service that provides secure and private channels to connect your VPCs to VPC endpoint services. It allows you to plan networks flexibly without having to use EIPs.
When installing VM agents in the VM environment, you can create VPC endpoints to communicate with Log Tank Service (LTS), Application Operations Management (AOM), Object Storage Service (OBS), and SoftWare Repository for Container (SWR), and use API Gateway (APIG) to call functional APIs of ServiceStage, ECS, VPC, and AOM based on configured private domain names.

Commercial use

How Can I Access Dependent Services Through VPC Endpoints When Installing VM Agents?

1

Tag policies

Tags are used to identify cloud resources. When you have multiple cloud resources of the same type, you can use tags to classify them based on usage, owner, or environment.
If your organization has configured tag policies for ServiceStage, add tags to trackers based on the policies.

Commercial use

Creating an Environment

1

ServiceStage stack supports OpenJDK11 and OpenJDK17

ServiceStage stack supports OpenJDK11 and OpenJDK17.

Commercial use

Component Overview

1

Enhanced deployment capability

Component deployment modes such as single-batch release, rolling release, and dark launch (canary) are provided.

Commercial use

Upgrading a Single Component

2

New console

A new console simplifies the component creation and deployment process and improves user experience.

Commercial use

Console Description

1

ServiceStage supports component deployment in a Kubernetes environment using the YAML configuration file

This service allows you to preview and modify Kubernetes-deployed templates so that you can deploy components in a Kubernetes environment using the YAML configuration file.

Commercial use

Creating and Deploying a Component

1

HPA policy

HPA is a built-in component of Kubernetes, which enables horizontal scaling of pods. It supports the application-level cooldown time window and scaling threshold functions based on the Kubernetes HPA.

Commercial use

Managing HPA Policies

2

Cluster-deployed exclusive microservice engines

An exclusive microservice engine of version 1.3.0 or later supports cluster-deployed exclusive microservice engines. Its support HA and host-level DR.

Commercial use

Exclusive Microservice Engine Types

3

APM 2.0 probe

ServiceStage allows you to configure application performance management during or after application component deployment.

The Application Performance Management (APM) service helps you quickly locate application problems and analyze performance bottlenecks, improving user experience.

Selecting APM 2.0 Java probe will start APM and install Java probes on the nodes deployed with APM, which consumes a small amount of resources.

Commercial use

Configuring Application Performance Management

1

Microservice engine security authentication

The exclusive microservice engine with security authentication enabled provides the system management function using the role-based access control (RBAC) through the microservice console.

Commercial use

System Management