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

Cluster FAQ

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 2024-12-12 17:59:35

Cluster Creation

Can I choose not to set a public IP address for the CVM when creating a cluster?

Yes. A CVM instance without a public IP address can only pull images from "My Images" in Image Repository, but cannot pull images from Docker Hub or third-party platforms. A CVM without a public IP address but with Internet bandwidth can access the Internet by binding an EIP.

Why do I need to choose a network when creating a cluster?

The selected network and subnet are where the CVM resides. You can add different CVMs to subnets in different AZs for cross-AZ disaster recovery.

What CVM models are supported when creating a cluster?

We offer Standard, Computing, High-IO, GPU, and BM CVM instances, as displayed in the TKE console.

What operating systems are supported for TKE hosts?

For more information on the currently operating systems supported by TKE, see Public Image List.

How do I customize Kubelet parameters for a TKE node?

This feature is made available through an allowlist. To use it, submit a ticket for application.
Customize kubelet parameters of a node on the Add Node page, Add Exiting Node page, or Create Node Pool page.



How do I customize Kubernetes component parameters when creating a TKE cluster?

For detailed directions, see Custom Kubernetes Component Launch Parameters.

Does TKE support self-deployed clusters?

TKE provides an independent Master deployment mode in which you have full control over your cluster. In this mode, the Master and Etcd of the Kubernetes cluster are deployed on the CVM instances you purchased, and you have all the management and operation permissions for the Kubernetes cluster. For more information, see Independent Master Deployment Mode.

Can I modify the AZ after a TKE serverless cluster is created?

After a TKE serverless cluster is created successfully, you cannot change or add AZs.

Can I get IPv6 addresses of TKE clusters on the client?

No.

Can I export the TKE cluster configuration?

No.

When a TKE cluster is created, the system prompts me to complete node exception detection plus parameter settings. What should I do?

If you are prompted to complete node exception detection plus parameter settings when creating a cluster, you need to check whether the NodeProblemDetectorPlus add-on is selected and configure the parameters if so. For more information, see NodeProblemDetectorPlus Add-on.
Note:
If you are unable to evaluate whether you need this add-on, we recommend you create the cluster directly without selecting it. If you need to use it later, simply install it in add-on management.

How do I enable IPVS for TKE clusters?

For detailed directions, see Enabling IPVS for a Cluster.

How do I view TKE cluster access credentials?

1. Log in to the TKE console and click Cluster in the left sidebar to enter the cluster management page.
2. Click the ID or name of the target cluster to enter the cluster details page.
3. Click Basic information in the left sidebar. You can view information such as the access address, public network/private network access status, and kubeconfig access credential of the cluster in the Cluster APIServer information section of the Basic information page.

How do I add CVM instances under other accounts to a TKE cluster?

Currently, you cannot add CVM instances under other accounts to a cluster. You can only add CVM instances in the same VPC.

What should I do if "certificate verify failed: self signed certificate" is reported when I use the Kubernetes SDK to connect the API server of the cluster?

As the API server in a Kubernetes cluster usually uses a self-signed TLS certificate, which is not trusted by the request library on an earlier Python version or the default settings of Node.js, an error will be reported. This error can be fixed in the following steps:
1. Add the configuration to skip server authentication. If you use the Node.js SDK, you need to set the environment variable:
export NODE_TLS_REJECT_UNAUTHORIZED="0";
If you use the Python SDK, you need to set it in kubeconfig.
clusters:
- cluster:
insecure-skip-tls-verify: true
2. Put the public key of the root certificate of the self-signed certificate issuing authority in the list of trusted root certificates of the system.

Cluster Network

What should I do for the cluster network when I develop a custom webhook?

When you develop a custom webhook, do not block Pods under kube-system namespace; otherwise, you cannot use the cluster network normally.

Adding CVM Instances

What are the limitations on adding CVMs to a cluster?

You can only choose the CVMs in the same region as the cluster. But you may choose a different AZ to implement cross-AZ deployment of the cluster.

Is there a limit on the number of CVMs?

Yes. The number of pay-as-you-go CVMs cannot exceed the usage quota of the current account. For details, see CVM Overview.

CVM Termination

After a CVM instance is terminated, what will happen to the containers deployed on it?

When a CVM instance is terminated, the resources it contains, such as containers, will also be terminated. If the number of containers for a service drops below the expected number of running containers, the cluster will launch more containers in other CVM instances until the desired number is reached.

Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan