Node pools allow the creation of worker nodes with varying configurations. Nodes belonging to a single node pool have identical
characteristics.
Cisco Container Platform supports node pools of multiple types, such as vSphere and nodepool. A single Cisco Container Platform deployment can have only one type of node pool.
In the Cisco Container Platform vSphere implementation, a node pool has the following properties:
Labels and taints are optional parameters. All nodes that belong to a nodepool are tagged with labels and they are tainted.
Taints are key-value pairs, which are associated with an effect.
The following table describes the available effects.
Effect
|
Description
|
NoSchedule
|
Ensures that the pods that do not contain this taint are not scheduled on the node.
|
PreferNoSchedule
|
Ensures that Kubernetes avoids scheduling pods that do not contain this taint on the node.
|
NoExecute
|
Ensures that a pod is removed from the node if it is already running on the node, and is not scheduled on the node if it is
not yet running on the node.
|
Each cluster has a unique node pool. During cluster creation, each cluster is assigned a default node pool.
Cisco Container Platform supports the ability for different master and worker configurations. To be able to support this, two new optional parameters,
namely, master_node_pool and worker_node_pool are created as part of the cluster creation API. Upon cluster creation, the master node is created in the master-pool and
the worker nodes are created in the default-pool.
![](https://www.cisco.com/content/dam/en/us/td/i/templates/note.gif) Note |
You can not delete a master-pool when there is only one master node.
|