What's New

1

Fine-grained cluster management in non-HA environments

When a CCE cluster is bound in a non-HA Kubernetes environment, a namespace can be bound as the default namespace for isolating component build data and component instances.

Commercial use

Environment Overview

Binding a CCE Cluster

Binding a Namespace

2

Version configuration of a single microservice component bound to the registration center in dark launch

In addition to upgrading the version configuration of a single microservice component bound to the ServiceComb engine in dark launch, ServiceStage supports upgrading the version configuration of a single microservice component bound to the registry/configuration center in dark launch.

Commercial use

Upgrading a Component in Dark Launch Mode

3

Built-in technology stack extension

Supports the OpenJDK21 and Node.js18 technology stacks.

Commercial use

Technology Stack

4

Release management for components deployed in the VM environment

In addition to supporting release management for components deployed in the container environment, ServiceStage supports release management for components deployed in the VM environment.

Open beta testing

Release Management Overview

5

HA environment management

In a Kubernetes HA environment, two CCE clusters in different AZs can be bound to provide intra-city active-active HA capabilities for applications. This environment is suitable for deploying applications that need to meet intra-city HA requirements.

Commercial use

Environment Overview

Creating a Kubernetes Environment in Resource Management Mode

Binding a CCE Cluster

6

Setting component upgrade policies

In practice, component upgrade is a common scenario. Components deployed based on a container on ServiceStage support the following upgrade policies:

• RollingUpdate: New pods are created gradually, and then old pods are deleted.
• Recreate: Old pods are deleted, and then new pods are created.

Commercial use

Configuring a Component Upgrade Policy

7

Preferred rules in workload affinity/anti-affinity scheduling

• Preferred rules in workload affinity scheduling: Filters pods that require affinity by label. If a pod that meets the filter criteria has been running on a node within the node range specified by the node label, the scheduler will preferentially schedule the created pod to this node range.
• Preferred rules in workload anti-affinity scheduling: Filters one or more pods that require affinity by label. If a pod that meets the filter criteria has been running on a node within the node range specified by the node label, the scheduler will preferentially schedule the created pod to another node range.

Commercial use

Configuring a Scheduling Policy of a Component Instance

8

Compressing Java and Tomcat applications into packages for VM deployment

ServiceStage allows you to compress a Java or Tomcat application into a .zip or .tar.gz package for deploying a component on a VM.

Commercial use

Component Overview

How Do I Package a Java or Tomcat Application?

9

Importing a CCE workload to an application to create a component

The operations on the components created by importing CCE workloads are the same as those on ServiceStage. In this case, you can migrate existing CCE workloads, improving service efficiency and user experience.

Commercial use

Creating a Component by Importing a CCE Workload

10

WAR package deployment for Java applications

ServiceStage supports the deployment of Java application components that are packaged as a WAR package and developed based on the Spring Boot framework.

Commercial use

Component Overview

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

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

Creating and Deploying a Component Based on a VM

11

Configuration management

The configuration file can be used to manage parameters required for component running. System variables related to the environment, application, and component are referenced in a configuration file. When configurations are used for component deployment, these system variables are replaced with the actual values. This feature enables you to use one configuration file to flexibly deploy components in environments, improving service efficiency and user experience.

Commercial use

Configuration Overview

12

Component source extension

• If the component source is a software package, you can customize the HTTP/HTTPS software package address.
• For container-deployed components, you can set the image access credential.

Commercial use

Component Overview

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

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

Creating and Deploying a Component Based on a VM

13

Component draft

When creating and deploying a component, ServiceStage allows you to save the component configuration as a draft to prevent the configured parameters from being lost due to unpredict factors such as closing the page.

Commercial use

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

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

Creating and Deploying a Component Based on a VM

14

Technology stack management

In addition to the built-in technology stacks, ServiceStage provides the technology stack management function to meet your requirements for customizing technology stack versions and providing multiple runtime systems.

Commercial use

Technology Stack Management Overview

1

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

2

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

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 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?

2

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?

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

New console

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

Commercial use

Console Description

2

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

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