Overview
When you use the Service of public network CLB type, the CLB is generated for random availability zone in the VPC where the cluster resides by default. Currently, TKE Service of public network CLB allows you to specify availability zones, including availability zones in other regions. This document describes how to bind and specify availability zones for CLB Service across regions via the console and YAML.
Use Cases
The cross-region access or cross-VPC access of CLB must be supported. That is, the VPC where the CLB resides and the VPC where the cluster resides are not in the same VPC.
The availability zone of CLB must be specified to realize unified management of resources.
Note:
1. Cross-region binding is only available to bill-by-IP accounts.
2. If you need to use the CLB that is not in the same VPC as this cluster, you need to connect the VPCs of the current cluster and the CLB via CCN. 3. After the VPCs are connected, please submit a ticket to apply for this feature. Directions
You can bind and specify availability zones for CLB Service across regions via the console and YAML.
1. Log in to the TKE console and click Cluster in the left sidebar. 2. In the Cluster page, click the ID of the cluster for which you need to create a Service to go to the cluster management page.
3. Select Services and Routes > Service to go to the Service management page and click Create.
4. Configure the availability zone rules in the “Create Service” page. The configuration rules are as follows:
Service Access: select LoadBalancer (public network).
Note:
1. If you need to use the CLB that is not in the same VPC as this cluster, you need to connect the VPCs of the current cluster and the CLB via CCN. 2. After the VPCs are connected, please submit a ticket to apply for this feature. Sample 1
If you only need to specify the availability zone of the VPC where the cluster resides, for example, if the VPC of the cluster is located in Guangzhou, and you need to specify the CLB of Guangzhou Zone 1 for CLB Service, you can add the following annotations to the YAML of the Service:
service.kubernetes.io/service.extensiveParameters: '{"ZoneId":"ap-guangzhou-1"}'
Sample 2
If you need to use a CLB that is not in the VPC of the cluster, you can add the following annotations to the YAML of the Service:
service.cloud.tencent.com/cross-region-id: "ap-guangzhou"
service.cloud.tencent.com/cross-vpc-id: "vpc-646vhcjj"
Note:
If you need to specify the availability zone, you also need to add the annotations of sample 1.
Sample 3
Select an existing load balancer for remote access, as shown below:
service.cloud.tencent.com/cross-region-id: "ap-guangzhou"
service.kubernetes.io/tke-existed-lbid: "lb-342wppll"
Sample 4
The annotation in the service YAML is as follows:
apiVersion: v1
kind: Service
metadata:
annotations:
service.cloud.tencent.com/cross-region-id: "ap-chongqing"
service.cloud.tencent.com/cross-vpc-id: "vpc-mjekzyps"
name: echo-server-service
namespace: default
spec:
......
---
apiVersion: v1
kind: Service
metadata:
annotations:
service.cloud.tencent.com/cross-region-id: "ap-chongqing"
service.kubernetes.io/tke-existed-lbid: "lb-o8ugf2wb"
name: echo-server-service
namespace: default
spec:
......
Was this page helpful?