Tencent Cloud

Recent Pages

Modifying Native Nodes

Last updated: 2024-06-14 16:28:43

This document describes how to modify common parameters for native nodes.
Feature Items
Modify Location and Description
Cloud Tag
Location Description: Log in to Container Service Console and choose Cluster from the left sidebar. On the cluster list page, click the ID of the target cluster to go to the details page. Choose Node Management, select Worker Node, and click on the Node Pool tab. On the tab page, select a node pool to go to the node pool details page. Click Edit at the top right corner of the Node Pool Basic Information module, and modify the Tencent Cloud tag in Edit Parameter Settings.
Effective Range: existing nodes and newly added nodes.
Model
Location Description: Log in to Container Service Console and choose Cluster from the left sidebar. On the cluster list page, click the ID of the target cluster to go to the details page. Choose Node Management, select Worker Node, and click on the Node Pool tab. On the tab page, select a node pool to go to the node pool details page. Select the Node Startup Configuration Information module and edit the model information.
Effective Range: newly added nodes.
﻿
Note:
The host model does not support deletion. You can add other alternative models with the same specifications.
1. You can select up to 10 models (including the host model) in the same node pool.
2. The list of available instance types is filtered based on the availability zone of the node pool subnet and the existing network resource margin.
3. If the host model of the node pool is GPU instance, adding non-GPU instance types as alternative models is not supported.
System disk
The console does not currently support modifying system disk types and capacities. You can edit the relevant fields in the machinesets objects corresponding to the node pool using kubectl. (For details, see Creation Parameter Description). Changes will only apply to newly added nodes.
﻿
Note: Existing nodes do not support modifications to system disk types and capacities.
Data disk
Location Description: Log in to Container Service Console and choose Cluster from the left sidebar. On the cluster list page, click the ID of the target cluster to go to the details page. Choose Node Management, select Worker Node, and click on the Node Pool tab. On the tab page, select a node pool to go to the node pool details page. Select the Node Startup Configuration Information module and edit the data disk information.
Effective Range: newly added nodes.
Public network bandwidth
The console does not currently support modifying Public Network Bandwidth Binding. You can edit the relevant fields in the machinesets objects corresponding to the node pool using kubectl. (For details, see Enabling Public Network Access). Changes will only apply to newly added nodes.
Note: Existing nodes do not support modifications to the public network activation status.
Security group
Location Description: Log in to Container Service Console and choose Cluster from the left sidebar. On the cluster list page, click the ID of the target cluster to go to the details page. Choose Node Management, select Worker Node, and click on the Node Pool tab. On the tab page, select a node pool to go to the node pool details page. Select the Node Startup Configuration Information module and edit the security group information.
Effective Range: If you check "Inventory Update", then the changes (including deletion, updating, and appending) on this security group will apply to all nodes (including existing and newly added nodes) in the node pool. You are advised to perform the operation with caution. If you do not check "Inventory Update", the changes will only apply to newly added nodes.
Host name
Location Description: Log in to Container Service Console and choose Cluster from the left sidebar. On the cluster list page, click the ID of the target cluster to go to the details page. Choose Node Management, select Worker Node, and click on the Node Pool tab. On the tab page, select a node pool to go to the node pool details page. Select the Node Startup Configuration Information module and edit the host name information.
Effective Range: newly added nodes.
﻿
Note:
1. By default, the host naming pattern is consistent with the cluster's node hostname naming pattern.
2. When the cluster's node hostname naming pattern is set to automatic naming, this parameter cannot be modified. By default, the intranet IP address is used as the host name and the node's hostname.
3. When the cluster's node hostname naming pattern is set to manual naming, this parameter can be modified. You can use the intranet IP address or a custom name as the host name and the node's hostname.
Supports subnet
Location Description: Log in to Container Service Console and choose Cluster from the left sidebar. On the cluster list page, click the ID of the target cluster to go to the details page. Choose Node Management, select Worker Node, and click on the Node Pool tab. On the tab page, select a node pool to go to the node pool details page. Select the Node Startup Configuration Information module and edit the subnet information.
Effective Range: newly added nodes.
Elastic scaling
Location Description: Log in to Container Service Console and choose Cluster from the left sidebar. On the cluster list page, click the ID of the target cluster to go to the details page. Choose Node Management, select Worker Node, and click on the Node Pool tab. On the tab page, select a node pool to go to the node pool details page. Click Edit at the top right corner of the Operation Information module and modify AS.
Effective Range: newly added nodes.
﻿
Note: For details on the principles of use and operational limitations, see Node Scaling.
qGPU
Location Description: Log in to Container Service Console and choose Cluster from the left sidebar. On the cluster list page, click the ID of the target cluster to go to the details page. Choose Node Management, select Worker Node, and click on the Node Pool tab. On the tab page, select a node pool to go to the node pool details page. Click Edit at the top right corner of the Operation Information module and modify qGPU.
Effective Range: newly added nodes.
﻿
Note: Whether the qGPU can be enabled depends on the model and the driver. For details, see Using qGPU.
Label/Taint/Annotation
Location Description: Log in to [Container Service Console] and choose Cluster from the left sidebar. On the cluster list page, click the ID of the target cluster to go to the details page. Choose Node Management, select Worker Node, and click on the Node Pool tab. On the tab page, select a node pool to go to the node pool details page. Select the Parameter Setting module and edit the Label/Taint/Annotation information.
Effective Range: If you check "Inventory Update", then the changes (including deletion, updating, and appending) on Label/Annotation/Taint will apply to all nodes (including existing and newly added nodes) in the node pool. You are advised to perform the operation with caution. If you do not check "Inventory Update", the changes will only apply to newly added nodes.
Kubelet/Kernel/Nameserver/Host
Location Description: Log in to Container Service Console and choose Cluster from the left sidebar. On the cluster list page, click the ID of the target cluster to go to the details page. Choose Node Management, select Worker Node, and click on the Node Pool tab. On the tab page, select a node pool to go to the node pool details page. Select the Parameter Setting module and edit Management information.
Effective Range: If you check the "Inventory Update" field, then the changes (including deletion, updating, and appending) on Management will apply to all nodes (including existing and newly added nodes) in the node pool. You are advised to perform the operation with caution. If you do not check "Inventory Update", the changes will only apply to newly added nodes.
﻿
Note: Some Kubelet parameters may trigger a business pod restart when you apply the parameter settings to existing nodes. You are advised to perform the operation with caution after assessing the risks. For details, see Management Parameter Introduction.
﻿

Contact Us

Contact our sales team or business advisors to help your business.

Technical Support

Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

7x24 Phone Support

Feature Items	Modify Location and Description
Cloud Tag	Location Description: Log in to Container Service Console and choose Cluster from the left sidebar. On the cluster list page, click the ID of the target cluster to go to the details page. Choose Node Management, select Worker Node, and click on the Node Pool tab. On the tab page, select a node pool to go to the node pool details page. Click Edit at the top right corner of the Node Pool Basic Information module, and modify the Tencent Cloud tag in Edit Parameter Settings. Effective Range: existing nodes and newly added nodes.
Model	Location Description: Log in to Container Service Console and choose Cluster from the left sidebar. On the cluster list page, click the ID of the target cluster to go to the details page. Choose Node Management, select Worker Node, and click on the Node Pool tab. On the tab page, select a node pool to go to the node pool details page. Select the Node Startup Configuration Information module and edit the model information. Effective Range: newly added nodes. Note: The host model does not support deletion. You can add other alternative models with the same specifications. 1. You can select up to 10 models (including the host model) in the same node pool. 2. The list of available instance types is filtered based on the availability zone of the node pool subnet and the existing network resource margin. 3. If the host model of the node pool is GPU instance, adding non-GPU instance types as alternative models is not supported.
System disk	The console does not currently support modifying system disk types and capacities. You can edit the relevant fields in the machinesets objects corresponding to the node pool using kubectl. (For details, see Creation Parameter Description). Changes will only apply to newly added nodes. Note: Existing nodes do not support modifications to system disk types and capacities.
Data disk	Location Description: Log in to Container Service Console and choose Cluster from the left sidebar. On the cluster list page, click the ID of the target cluster to go to the details page. Choose Node Management, select Worker Node, and click on the Node Pool tab. On the tab page, select a node pool to go to the node pool details page. Select the Node Startup Configuration Information module and edit the data disk information. Effective Range: newly added nodes.
Public network bandwidth	The console does not currently support modifying Public Network Bandwidth Binding. You can edit the relevant fields in the machinesets objects corresponding to the node pool using kubectl. (For details, see Enabling Public Network Access). Changes will only apply to newly added nodes. Note: Existing nodes do not support modifications to the public network activation status.
Security group	Location Description: Log in to Container Service Console and choose Cluster from the left sidebar. On the cluster list page, click the ID of the target cluster to go to the details page. Choose Node Management, select Worker Node, and click on the Node Pool tab. On the tab page, select a node pool to go to the node pool details page. Select the Node Startup Configuration Information module and edit the security group information. Effective Range: If you check "Inventory Update", then the changes (including deletion, updating, and appending) on this security group will apply to all nodes (including existing and newly added nodes) in the node pool. You are advised to perform the operation with caution. If you do not check "Inventory Update", the changes will only apply to newly added nodes.
Host name	Location Description: Log in to Container Service Console and choose Cluster from the left sidebar. On the cluster list page, click the ID of the target cluster to go to the details page. Choose Node Management, select Worker Node, and click on the Node Pool tab. On the tab page, select a node pool to go to the node pool details page. Select the Node Startup Configuration Information module and edit the host name information. Effective Range: newly added nodes. Note: 1. By default, the host naming pattern is consistent with the cluster's node hostname naming pattern. 2. When the cluster's node hostname naming pattern is set to automatic naming, this parameter cannot be modified. By default, the intranet IP address is used as the host name and the node's hostname. 3. When the cluster's node hostname naming pattern is set to manual naming, this parameter can be modified. You can use the intranet IP address or a custom name as the host name and the node's hostname.
Supports subnet	Location Description: Log in to Container Service Console and choose Cluster from the left sidebar. On the cluster list page, click the ID of the target cluster to go to the details page. Choose Node Management, select Worker Node, and click on the Node Pool tab. On the tab page, select a node pool to go to the node pool details page. Select the Node Startup Configuration Information module and edit the subnet information. Effective Range: newly added nodes.
Elastic scaling	Location Description: Log in to Container Service Console and choose Cluster from the left sidebar. On the cluster list page, click the ID of the target cluster to go to the details page. Choose Node Management, select Worker Node, and click on the Node Pool tab. On the tab page, select a node pool to go to the node pool details page. Click Edit at the top right corner of the Operation Information module and modify AS. Effective Range: newly added nodes. Note: For details on the principles of use and operational limitations, see Node Scaling.
qGPU	Location Description: Log in to Container Service Console and choose Cluster from the left sidebar. On the cluster list page, click the ID of the target cluster to go to the details page. Choose Node Management, select Worker Node, and click on the Node Pool tab. On the tab page, select a node pool to go to the node pool details page. Click Edit at the top right corner of the Operation Information module and modify qGPU. Effective Range: newly added nodes. Note: Whether the qGPU can be enabled depends on the model and the driver. For details, see Using qGPU.
Label/Taint/Annotation	Location Description: Log in to [Container Service Console] and choose Cluster from the left sidebar. On the cluster list page, click the ID of the target cluster to go to the details page. Choose Node Management, select Worker Node, and click on the Node Pool tab. On the tab page, select a node pool to go to the node pool details page. Select the Parameter Setting module and edit the Label/Taint/Annotation information. Effective Range: If you check "Inventory Update", then the changes (including deletion, updating, and appending) on Label/Annotation/Taint will apply to all nodes (including existing and newly added nodes) in the node pool. You are advised to perform the operation with caution. If you do not check "Inventory Update", the changes will only apply to newly added nodes.
Kubelet/Kernel/Nameserver/Host	Location Description: Log in to Container Service Console and choose Cluster from the left sidebar. On the cluster list page, click the ID of the target cluster to go to the details page. Choose Node Management, select Worker Node, and click on the Node Pool tab. On the tab page, select a node pool to go to the node pool details page. Select the Parameter Setting module and edit Management information. Effective Range: If you check the "Inventory Update" field, then the changes (including deletion, updating, and appending) on Management will apply to all nodes (including existing and newly added nodes) in the node pool. You are advised to perform the operation with caution. If you do not check "Inventory Update", the changes will only apply to newly added nodes. Note: Some Kubelet parameters may trigger a business pod restart when you apply the parameter settings to existing nodes. You are advised to perform the operation with caution after assessing the risks. For details, see Management Parameter Introduction.

tencent cloud

Recent Pages

Modifying Native Nodes

Was this page helpful?

Was this page helpful?

tencent cloud

Sign Up

Log in

Recent Pages

Modifying Native Nodes

Was this page helpful?

Was this page helpful?