tencent cloud

Tencent Kubernetes Engine

Release Notes and Announcements
Release Notes
Announcements
Release Notes
Product Introduction
Overview
Strengths
Architecture
Scenarios
Features
Concepts
Native Kubernetes Terms
Common High-Risk Operations
Regions and Availability Zones
Service Regions and Service Providers
Open Source Components
Purchase Guide
Purchase Instructions
Purchase a TKE General Cluster
Purchasing Native Nodes
Purchasing a Super Node
Getting Started
Beginner’s Guide
Quickly Creating a Standard Cluster
Examples
Container Application Deployment Check List
Cluster Configuration
General Cluster Overview
Cluster Management
Network Management
Storage Management
Node Management
GPU Resource Management
Remote Terminals
Application Configuration
Workload Management
Service and Configuration Management
Component and Application Management
Auto Scaling
Container Login Methods
Observability Configuration
Ops Observability
Cost Insights and Optimization
Scheduler Configuration
Scheduling Component Overview
Resource Utilization Optimization Scheduling
Business Priority Assurance Scheduling
QoS Awareness Scheduling
Security and Stability
TKE Security Group Settings
Identity Authentication and Authorization
Application Security
Multi-cluster Management
Planned Upgrade
Backup Center
Cloud Native Service Guide
Cloud Service for etcd
TMP
TKE Serverless Cluster Guide
TKE Registered Cluster Guide
Use Cases
Cluster
Serverless Cluster
Scheduling
Security
Service Deployment
Network
Release
Logs
Monitoring
OPS
Terraform
DevOps
Auto Scaling
Containerization
Microservice
Cost Management
Hybrid Cloud
AI
Troubleshooting
Disk Full
High Workload
Memory Fragmentation
Cluster DNS Troubleshooting
Cluster kube-proxy Troubleshooting
Cluster API Server Inaccessibility Troubleshooting
Service and Ingress Inaccessibility Troubleshooting
Common Service & Ingress Errors and Solutions
Engel Ingres appears in Connechtin Reverside
CLB Ingress Creation Error
Troubleshooting for Pod Network Inaccessibility
Pod Status Exception and Handling
Authorizing Tencent Cloud OPS Team for Troubleshooting
CLB Loopback
API Documentation
History
Introduction
API Category
Making API Requests
Elastic Cluster APIs
Resource Reserved Coupon APIs
Cluster APIs
Third-party Node APIs
Relevant APIs for Addon
Network APIs
Node APIs
Node Pool APIs
TKE Edge Cluster APIs
Cloud Native Monitoring APIs
Scaling group APIs
Super Node APIs
Other APIs
Data Types
Error Codes
TKE API 2022-05-01
FAQs
TKE General Cluster
TKE Serverless Cluster
About OPS
Hidden Danger Handling
About Services
Image Repositories
About Remote Terminals
Event FAQs
Resource Management
Service Agreement
TKE Service Level Agreement
TKE Serverless Service Level Agreement
Contact Us
Glossary
DokumentasiTencent Kubernetes EngineApplication ConfigurationService and Configuration Management Service ManagementService Cross-region Binding

Service Cross-region Binding

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 2024-12-23 11:41:09

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.
4. You should enter the region ID in the following YAML. You can check the region ID in Regions and Availability Zones.

Directions

You can bind and specify availability zones for CLB Service across regions via the console and YAML.
Console
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:
# Create a CLB for remote access
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: 
  ...... 
--- 
# Use the existing CLB of other region
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: 
  ...... 

For detailed Service annotations, please see Service Annotation.
Topik sebelumnya: Service Backend SelectionTopik selanjutnya: Graceful Service Shutdown

Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan