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.
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.
We offer Standard, Computing, High-IO, GPU, and BM CVM instances, as displayed in the TKE console.
For more information on the currently operating systems supported by TKE, see Public Image List
For detailed directions, see Custom Kubernetes Component Launch Parameters.
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.
After a TKE serverless cluster is created successfully, you cannot change or add AZs.
No.
No.
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.
For detailed directions, see Enabling IPVS for a Cluster.
Currently, you cannot add CVM instances under other accounts to a cluster. You can only add CVM instances in the same VPC.
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:
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
When you develop a custom webhook, do not block Pods under kube-system namespace
; otherwise, you cannot use the cluster network normally.
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.
Yes. The number of pay-as-you-go CVMs cannot exceed the usage quota of the current account. For details, see CVM Overview.
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.
Was this page helpful?