nodePoolList
nodePoolList
JSON Example
{
"items": [
{
"cloneMode": "string",
"cpu": 0,
"id": "string",
"labels": [
"string"
],
"memory": 0,
"name": "string",
"networks": [
{
"label": "string",
"networkName": "string",
"networkFullPath": "string",
"mtu": 0,
"isManagement": false,
"derivedFromCsar": false,
"nameservers": [
"string"
]
}
],
"placementParams": [
{
"name": "string",
"type": "string"
}
],
"replica": 0,
"storage": 0,
"config": {
"cpuManagerPolicy": {
"type": "string",
"policy": "string",
"properties": {
"kubeReserved": {
"cpu": 0,
"memoryInGiB": 0
},
"systemReserved": {
"cpu": 0,
"memoryInGiB": 0
}
}
},
"healthCheck": {
"nodeStartupTimeout": "string",
"unhealthyConditions": [
{
"type": "string",
"status": "string",
"timeout": "string"
}
]
}
},
"status": "string",
"activeTasksCount": 0,
"nodes": [
{
"ip": "string",
"vmName": "string"
}
],
"isNodeCustomizationDeprecated": false,
"warnings": [
{
"operationType": "string",
"message": "string",
"errorCode": "string",
"internalMessage": "string"
}
],
"errors": [
{
"operationType": "string",
"message": "string",
"errorCode": "string",
"internalMessage": "string"
}
]
}
]
}array of nodePool
items
Optional
Pool of worker nodes on which Network Functions can run. Each Node Pool can be deployed on a vSphere Resource Pool. All the worker nodes in a node pool contain same Kubelet and Operating System Configuration. It is recommended that a Node Pool should be used by only one Network Function, if it has Infrastructure requirements.