Docs

Code Pipeline

Access methods

Add intranet load balancing

Add internal load balancing for the application to enable other applications within the same VPC to access the current application. This article introduces how to add intranet load balancing.

Prerequisites

A managed application has been created and deployed, and the application must be deployed in a Volcengine Kubernetes Engine (VKE) cluster. For specific operations, refer to Create and deploy managed applications (JAR /WAR).

The Volcano Engine Load Balancer has been activated.

If you use an existing CLB instance, please create it in advance. For specific operations, refer to create a load balancing instance.

If you choose to automatically create a CLB instance, please ensure that your account balance is sufficient; otherwise, creation may fail.

Limit

Modification protection will be turned on for CLB instances automatically created by CP. Do not directly manually modify the instance content through the load balancing console.

CLB instances automatically created by CP are deleted synchronously when the service is deleted.

When using an existing CLB instance, you cannot select instances automatically created by other Product, in order to avoid configuration conflicts between services.

danger

Do not manually modify listeners and backend server groups maintained by CP (with names containing the k8s_ prefix) via the load balancing console, as this may result in rollback of configuration changes made in the load balancing console and cause failures related to application ingress.

Procedure

In the left navigation bar, select workspace.

Click the name of the target workspace to enter the current workspace.

In the left navigation bar, select Application Delivery > Application Management.

On the application management page, select the target hosted application, click the application card, and go to the basic information tab for the current application.

Switch to the application orchestration tab. In the access method settings section, select Load Balancer (Intranet) > Add Load Balancer (Intranet).

In the Add Load Balancer (Intranet) dialog box, set load balancer parameters.

Configuration Item	Descriptions
Load balancer CLB	Configuration of the service load balancer supports automatic creation or using an existing one. Unless there are special circumstances, it is recommended to select automatic creation. Automatic creation: A brand-new CLB instance will be automatically created for you by CP. Instances will use the following default configuration and modification is not supported. Name: Automatically generated by the system, with the format K8s-xxx. Instance specification: Medium I. Subnet: Randomly selects one of the subnets under your account as the default subnet. Instance protection: Turn on instance modification protection. IP version: IPv4. Billing method: Pay-as-you-go. For detailed billing standards, refer to product billing. warning Do not manually modify automatically created CLB instances directly in the load balancing console. CLB instances that are created automatically will be deleted synchronously when the service is deleted. Do not use an automatically created CLB for other resources to avoid resource remnants or accidental deletion. Automatically created CLB instances support multi-availability zone capability. If the load balancer in the current Region supports cross-availability zone disaster recovery, a load balancer instance with primary and standby availability zones will be created by default. When the primary availability zone fails, traffic will be switched to the standby availability zone to ensure uninterrupted business operations. Use existing: Supports using CLB instances that are not automatically created by the system. No restriction on billing type. warning Selecting CP or other products to automatically create CLB instances is not supported. When using an existing CLB instance, do not overwrite the listener rules that already exist on the instance. CP will configure new listeners and backend server groups under your CLB instance. Please do not modify the related configuration in the load balancing console on your own.
Scheduling algorithm	Rules that must be followed when specifying listener request forwarding. Weighted Round Robin: traffic is forwarded based on weight values. The higher the weight of the backend server, the more frequently (probabilistically) it is selected as the forwarding destination. Weighted Least Connection: traffic is forwarded first to the backend with the smallest real-time ratio of connections to weight. Source Hashing: traffic is always forwarded to a single backend server if the hash of the source IP remains unchanged.
Port mapping	Configure port mapping rules. Supports configuration of multiple port mappings. tip Multiple port mappings are commonly used in scenarios where an application defines several ports to distinguish between different features. For example: one port is used for business access, and another port is used for debugging. When adding multiple port mappings, server ports must not be duplicated. Service port: Defines the frontend port for internal network load balancing. The application can be accessed through this port, and the port number can be set within the range of 1 to 65535. Protocol: Select a communication protocol. Supported protocols: TCP and UDP. Container port: The port that a process listens on, typically defined by the program. For example, the Web application uses port 8080 by default.
External traffic policy	The policy for forwarding external traffic in Service currently only supports Cluster. Cluster: Traffic can be evenly distributed to all instances corresponding to the application.

Click confirm. The internal load balancer will begin to be created.

tip

The key specifications of CLB include maximum number of connections, number of connections created per second, and number of queries per second. If the traffic to your application exceeds the specification limits of CLB, you can add multiple CLBs to distribute the traffic load.

Result validation

View the port mapping for the load balancer (internal network) in the table: <Load balancer IP>:<Port number>.

Using a machine with internal network access permission, enter <load balancer IP>:<port number> in the browser address bar. For example, 192.xx.xx.xx:80. You will be able to successfully access the application homepage.

Related Operations

For an already created load balancing (internal network) type Service, modifying the scheduling algorithm, port mapping, and other information is supported, as well as deleting the Service.

Feature	Descriptions
Modify the Service	Select the target load balancing Service, click edit in the Actions column, and modify the relevant information. warning Modifying the scheduling algorithm here will override the configuration in the CLB console. Please modify with caution.
Delete a service	Select the target load balancing Service, click Actions in the column, then click delete to delete the current Service. danger After you delete the service, the internal CLB instance automatically created by CP will be physically deleted. Applications within the same VPC will not be able to access your application through the internal CLB port. Please exercise caution when performing actions!

Last updated: 2025.09.10 17:37:26