Release Notes and Announcements
- Release Notes
- Announcements
- Release Notes
Product Introduction
Purchase Guide
- Purchase Instructions
- Purchase a TKE General Cluster
- Purchasing Native Nodes
- Purchasing a Super Node
Getting Started
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
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

Multi-AZ Adjustment for Nodes

Mode fokus

Ukuran font

Terakhir diperbarui: 2025-03-19 18:30:13

Overview
This document describes multi-AZ adjustment for nodes of etcd clusters in the console.
Note:
Node addition (increasing the number of nodes) does not affect normal business operation.
Node removal (decreasing the number of nodes) may trigger a leader election in the cluster. It is recommended to perform this operation at off-peak hours.
Prerequisites
etcd cluster have been created.
Viewing AZ Distribution of Cluster Nodes
1. Log in to the console of Cloud Service for etcd.
2. Go to the etcd cluster list page, select the region at the top of the page, and find the target etcd cluster in the cluster list below.
3. View the AZ distribution of nodes on the node management page, as shown in the figure below:
﻿
Viewing AZ Distribution of Subnets and Adding Subnets in Different AZs
1. Log in to the console of Cloud Service for etcd.
2. Go to the etcd cluster list page, select the region at the top of the page, and find the target etcd cluster in the cluster list below.
3. Go to the basic information page and view the AZ distribution of current subnets and the button for adding subnets, as shown in the figure below:
﻿
4. Click Add subnet, select subnets in different AZs, and click Confirm. If high availability deployment is enabled, subnets in at least three AZs are required.
Multi-AZ Adjustment Methods
Number of Cluster Nodes
Actual Number of AZs in the Region
Number of AZs for Current Cluster Subnets
Actual Number of AZs for Cluster Nodes
Multi-AZ Adjustment Method
1 node
1 AZ
1 AZ
1 AZ
N/A
﻿
2 AZs
1 AZ
1 AZ
Add 1 subnet in a different AZ, and increase the number of nodes to 3.
﻿
﻿
2 AZs
1 AZ
Increase the number of nodes to 3.
﻿
≥ 3 AZs
1 AZ
1 AZ
Add 2 subnets in different AZs, and increase the number of nodes to 3.
﻿
﻿
2 AZs
1 AZ
Add 1 subnet in a different AZ, and increase the number of nodes to 3.
﻿
﻿
≥ 3 AZs
1 AZ
Increase the number of nodes to 3.
3 nodes
1 AZ
1 AZ
1 AZ
N/A
﻿
2 AZs
1 AZ
1 AZ
Add 1 subnet in a different AZ, and increase the number of nodes to 5.
﻿
﻿
2 AZs
1 AZ
Increase the number of nodes to 5.
﻿
﻿
2 AZs
2 AZs
N/A
﻿
≥ 3 AZs
1 AZ
1 AZ
Add 2 subnets in different AZs, and increase the number of nodes to 5.
﻿
﻿
2 AZs
1 AZ
Add 1 subnet in a different AZ, and increase the number of nodes to 5.
﻿
﻿
2 AZs
2 AZs
Add 1 subnet in a different AZ, and increase the number of nodes to 5.
﻿
﻿
≥ 3 AZs
1 AZ
Increase the number of nodes to 5.
﻿
﻿
≥ 3 AZs
2 AZs
Increase the number of nodes to 5.
﻿
﻿
≥ 3 AZs
≥ 3 AZs
N/A
5 nodes
1 AZ
1 AZ
1 AZ
N/A
﻿
2 AZs
1 AZ
1 AZ
Add 1 subnet in a different AZ, decrease the number of nodes to 3, and then increase the number of nodes to 5.
﻿
﻿
2 AZs
1 AZ
Decrease the number of nodes to 3, and then increase the number of nodes to 5.
﻿
﻿
2 AZs
2 AZs
N/A
﻿
≥ 3 AZs
1 AZ
1 AZ
Add 2 subnets in different AZs, decrease the number of nodes to 3, and then increase the number of nodes to 5.
﻿
﻿
2 AZs
1 AZ
Add 1 subnet in a different AZ, decrease the number of nodes to 3, and then increase the number of nodes to 5.
﻿
﻿
2 AZs
2 AZs
Add 1 subnet in a different AZ, decrease the number of nodes to 3, and then increase the number of nodes to 5.
﻿
﻿
≥ 3 AZs
1 AZ
Decrease the number of nodes to 3, and then increase the number of nodes to 5.
﻿
﻿
≥ 3 AZs
2 AZs
Decrease the number of nodes to 3, and then increase the number of nodes to 5.
﻿
﻿
≥ 3 AZs
≥ 3 AZs
N/A

Bantuan dan Dukungan

Apakah halaman ini membantu?

Anda juga dapat Menghubungi Penjualan atau Mengirimkan Tiket untuk meminta bantuan.

masukan

tencent cloud

Tencent Kubernetes Engine

Multi-AZ Adjustment for Nodes

Overview

Prerequisites

Viewing AZ Distribution of Cluster Nodes

Viewing AZ Distribution of Subnets and Adding Subnets in Different AZs

Multi-AZ Adjustment Methods

Bantuan dan Dukungan

Number of Cluster Nodes	Actual Number of AZs in the Region	Number of AZs for Current Cluster Subnets	Actual Number of AZs for Cluster Nodes	Multi-AZ Adjustment Method
1 node	1 AZ	1 AZ	1 AZ	N/A
		2 AZs	1 AZ	1 AZ	Add 1 subnet in a different AZ, and increase the number of nodes to 3.
		2 AZs		2 AZs	1 AZ	Increase the number of nodes to 3.
		≥ 3 AZs	1 AZ	1 AZ	Add 2 subnets in different AZs, and increase the number of nodes to 3.
				2 AZs	1 AZ	Add 1 subnet in a different AZ, and increase the number of nodes to 3.
				≥ 3 AZs	1 AZ	Increase the number of nodes to 3.
3 nodes	1 AZ	1 AZ	1 AZ	N/A
		2 AZs	1 AZ	1 AZ	Add 1 subnet in a different AZ, and increase the number of nodes to 5.
				2 AZs	1 AZ	Increase the number of nodes to 5.
				2 AZs	2 AZs	N/A
		≥ 3 AZs	1 AZ	1 AZ	Add 2 subnets in different AZs, and increase the number of nodes to 5.
				2 AZs	1 AZ	Add 1 subnet in a different AZ, and increase the number of nodes to 5.
				2 AZs	2 AZs	Add 1 subnet in a different AZ, and increase the number of nodes to 5.
				≥ 3 AZs	1 AZ	Increase the number of nodes to 5.
				≥ 3 AZs	2 AZs	Increase the number of nodes to 5.
				≥ 3 AZs	≥ 3 AZs	N/A
5 nodes	1 AZ	1 AZ	1 AZ	N/A
		2 AZs	1 AZ	1 AZ	Add 1 subnet in a different AZ, decrease the number of nodes to 3, and then increase the number of nodes to 5.
				2 AZs	1 AZ	Decrease the number of nodes to 3, and then increase the number of nodes to 5.
				2 AZs	2 AZs	N/A
		≥ 3 AZs	1 AZ	1 AZ	Add 2 subnets in different AZs, decrease the number of nodes to 3, and then increase the number of nodes to 5.
				2 AZs	1 AZ	Add 1 subnet in a different AZ, decrease the number of nodes to 3, and then increase the number of nodes to 5.
				2 AZs	2 AZs	Add 1 subnet in a different AZ, decrease the number of nodes to 3, and then increase the number of nodes to 5.
				≥ 3 AZs	1 AZ	Decrease the number of nodes to 3, and then increase the number of nodes to 5.
				≥ 3 AZs	2 AZs	Decrease the number of nodes to 3, and then increase the number of nodes to 5.
				≥ 3 AZs	≥ 3 AZs	N/A