Configurations

Apply max-pod-pids, podPidsLimit

• Simultaneous operation of 3 worker nodes

• Recommended method: Modify config.yaml (based on Kubeadm)

  • /etc/kubernetes/kubelet-config.yaml (if not present, then)
  • /var/lib/kubelet/config.yaml

• How to edit:
  1. Make sure the file has a podPidsLimit field. (없으면 추가)
  2. Set the value.

# /var/lib/kubelet/config.yaml
     apiVersion: kubelet.config.k8s.io/v1beta1
     kind: KubeletConfiguration
     ...
     podPidsLimit: 4096  # 이 줄을 추가
     ...

• Application Process (Important)
  1. If you have modified the configuration file, you must allow the Kubelet to read it again.
  Restart the Kubelet after modifying the configuration

systemctl daemon-reload
     systemctl restart kubelet

2. Check whether the settings are reflected:
   Check whether the settings were actually applied using the following command within the node.

# Kubelet 설정 덤프 확인
     kubectl get --raw "/api/v1/nodes/<노드이름>/proxy/configz" | jq | grep podPidsLimit

• Summary and precautions
• If you want to put it directly in /etc/kubernetes/kubelet.env, you need to put it in the flag format called -pod-max-pids=4096.
• However, the standard for recent clusters is to write podPidsLimit: 4096 inside /var/lib/kubelet/config.yaml.