Перевірити так
kubectl get nodes -o json | jq '.items[] | {name: .metadata.name, cap: .status.capacity}'
kube@kub01pp:/etc/systemd/system/kubelet.service.d$ kubectl get nodes -o json | jq '.items[] | {name: .metadata.name, cap: .status.capacity}'
Щоб було як у у прикладі 240, а не 110
{
"name": "kub01pp",
"cap": {
"cpu": "16",
"ephemeral-storage": "38703652Ki",
"hugepages-1Gi": "0",
"hugepages-2Mi": "0",
"memory": "65963632Ki",
"pods": "240"
}
}
{
"name": "kub02pp",
"cap": {
"cpu": "16",
"ephemeral-storage": "38703652Ki",
"hugepages-1Gi": "0",
"hugepages-2Mi": "0",
"memory": "65963572Ki",
"pods": "240"
}
}
{
"name": "kub03pp",
"cap": {
"cpu": "16",
"ephemeral-storage": "0",
"hugepages-1Gi": "0",
"hugepages-2Mi": "0",
"memory": "65963632Ki",
"pods": "240"
}
}
cd /etc/systemd/system/kubelet.service.d/
у цьому файлі додати Environment="KUBELET_EXTRA_ARGS=--max-pods=240" 10-kubeadm.conf
потім systemctl daemon-reload
service kubelet restart
kubectl get nodes -o json | jq '.items[] | {name: .metadata.name, cap: .status.capacity}'
kube@kub01pp:/etc/systemd/system/kubelet.service.d$ kubectl get nodes -o json | jq '.items[] | {name: .metadata.name, cap: .status.capacity}'
Щоб було як у у прикладі 240, а не 110
{
"name": "kub01pp",
"cap": {
"cpu": "16",
"ephemeral-storage": "38703652Ki",
"hugepages-1Gi": "0",
"hugepages-2Mi": "0",
"memory": "65963632Ki",
"pods": "240"
}
}
{
"name": "kub02pp",
"cap": {
"cpu": "16",
"ephemeral-storage": "38703652Ki",
"hugepages-1Gi": "0",
"hugepages-2Mi": "0",
"memory": "65963572Ki",
"pods": "240"
}
}
{
"name": "kub03pp",
"cap": {
"cpu": "16",
"ephemeral-storage": "0",
"hugepages-1Gi": "0",
"hugepages-2Mi": "0",
"memory": "65963632Ki",
"pods": "240"
}
}
cd /etc/systemd/system/kubelet.service.d/
у цьому файлі додати Environment="KUBELET_EXTRA_ARGS=--max-pods=240" 10-kubeadm.conf
потім systemctl daemon-reload
service kubelet restart
Комментариев нет:
Отправить комментарий