ㅁ kubelet.conf 파일 위치
/etc/systemd/system/kubelet.service.d/
아래에
10-kubeadm.conf
내용을 보면 주요 설정 내용이 있다
$ cat /etc/systemd/system/kubelet.service.d/10-kubeadm.conf
# Note: This dropin only works with kubeadm and kubelet v1.11+
[Service]
Environment="KUBELET_KUBECONFIG_ARGS=--bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf"
Environment="KUBELET_CONFIG_ARGS=--config=/var/lib/kubelet/config.yaml"
# This is a file that "kubeadm init" and "kubeadm join" generates at runtime, populating the KUBELET_KUBEADM_ARGS variable dynamically
EnvironmentFile=-/var/lib/kubelet/kubeadm-flags.env
# This is a file that the user can use for overrides of the kubelet args as a last resort. Preferably, the user should use
# the .NodeRegistration.KubeletExtraArgs object in the configuration files instead. KUBELET_EXTRA_ARGS should be sourced from this file.
EnvironmentFile=-/etc/default/kubelet
ExecStart=
ExecStart=/usr/bin/kubelet $KUBELET_KUBECONFIG_ARGS $KUBELET_CONFIG_ARGS $KUBELET_KUBEADM_ARGS $KUBELET_EXTRA_ARGS
여러 설정 파일을 조사해 보면
/etc/kubernetes/kubelet.conf
apiVersion: v1
clusters:
- cluster:
certificate-authority-data: LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUM1ekNDQWMrZ0F3SUJBZ0lCQURBTkJna3Foa2lHOXcwQkFRc0ZBREFWTVJNd0VRWURWUVFERXdwcmRXSmwKY201bGRHVnpNQjRYRFRJeE1EUXdNVEV6TVRBeE1Gb1hEVE14TURNek1ERXpNVEF4TUZvd0ZURVRNQkVHQTFVRQpBeE1LYTNWaVpYSnVaWFJsY3pDQ0FTSXdEUVlKS29aSWh2Y05BUUVCQlFBRGdnRVBBRENDQVFvQ2dnRUJBTldICkJXbFV1czJyRUxoMVE5Y2dqSWlVek9qWlpmaVkxd1BIbUxUclh6Nm5HaitGbFFVOXpmWTlyejVYbC9GN3BWVjQKaE81Q2NlNzFNVTk2a0NESzRrSlc2N29RSlBkbWdIUytIRW9oY1RkK0IyVm9LY3lGOUdGRUIxQUMrNlo5QzhBRwo5UHMyUG83UkxhRENQS2VWK2RjbUdVbmpubGxpbUorNThEQVdnU0VYbVZWUjFYdFdpM0VKSlRIWENrT3RsVm91CmpDOUQvajZxaFJGZlhkNVNicXpuVnNJYVMvekoyQ2V0dHhlbmVOOUlPNHIzOHJPRUREMEVFaW5oamNKV0FZRG8KTG0veXlsdlFIVEt4UzcyZUUweFg0SWxub1krS1V1QmFIakJjZFNhV3FBN0w1ZkNiSHJMUjV4aGxicW9DR25KSgoxL09VRmpyQUMxMHdVVG90TTNrQ0F3RUFBYU5DTUVBd0RnWURWUjBQQVFIL0JBUURBZ0trTUE4R0ExVWRFd0VCCi93UUZNQU1CQWY4d0hRWURWUjBPQkJZRUZLeEowbFo0UHRuOXdMTHlaeXdoK3ROSDllZk9NQTBHQ1NxR1NJYjMKRFFFQkN3VUFBNElCQVFDV0QwVDg5NGRhQXJ4dGJWUFdrTGVIVGJZZGZFcWljUTNURjhJRTdSbHNzUTBKZGtaNQpvWm5mOGVhWkNaV3JTWjFxQWtjaFVyWU5wRlcvN29lOFp4cW1CK05OOEpubzljOE5xdFJHTnBFbWdWd09wREZPCllBS0RmOHBmVkJqTlRiNHdxSTJ0ZXRKR09UZ1JnTVRRcjRtaHhRRUJ5cUxMbWFKYU9MdkpNeWxPRVVxOWt5aGIKMUNub0IrM0w2QTZBQVdtNTVrZzkzb3A2eVNSeDhnUUFHRUNPWkxmMHVrczZNUnk4YXNFcWpXTVZCam1ESmZnRwpueWRPKzdWUHJndGhKek5TSTd0d3dMeXdqYTArVXI0bloyck9hb1NrQlgrRXpYSlRJMWREd2FzemlxaXlFNkp1CnRKV0pHUnNvVDNLQUZrY2NuYWJ0YUtxNXRjSWE1WlR3b0R4SgotLS0tLUVORCBDRVJUSUZJQ0FURS0tLS0tCg==
server: https://172.17.0.22:6443
name: default-cluster
contexts:
- context:
cluster: default-cluster
namespace: default
user: default-auth
name: default-context
current-context: default-context
kind: Config
preferences: {}
users:
- name: default-auth
user:
client-certificate: /var/lib/kubelet/pki/kubelet-client-current.pem
client-key: /var/lib/kubelet/pki/kubelet-client-current.pem
/var/libe/kubelet/config.yaml
apiVersion: kubelet.config.k8s.io/v1beta1
authentication:
anonymous:
enabled: false
webhook:
cacheTTL: 0s
enabled: true
x509:
clientCAFile: /etc/kubernetes/pki/ca.crt
authorization:
mode: Webhook
webhook:
cacheAuthorizedTTL: 0s
cacheUnauthorizedTTL: 0s
cgroupDriver: systemd
clusterDNS:
- 10.96.0.10
clusterDomain: cluster.local
cpuManagerReconcilePeriod: 0s
evictionPressureTransitionPeriod: 0s
fileCheckFrequency: 0s
healthzBindAddress: 127.0.0.1
healthzPort: 10248
httpCheckFrequency: 0s
imageMinimumGCAge: 0s
kind: KubeletConfiguration
logging: {}
nodeStatusReportFrequency: 0s
nodeStatusUpdateFrequency: 0s
resolvConf: /run/systemd/resolve/resolv.conf
rotateCertificates: true
runtimeRequestTimeout: 0s
staticPodPath: /etc/kubernetes/manifests
streamingConnectionIdleTimeout: 0s
syncFrequency: 0s
volumeStatsAggPeriod: 0s
여기에서 오류 내용들을 찾아서 수정한다.
systemctl daemon-reload
service kubelet restart
master node에서 kube clutser 관련 기본 정보도 확인한다.
kubectl cluster-info
'CKA &. CKAD > Troubleshooting' 카테고리의 다른 글
kubelet 주요 이슈 확인 (0) | 2021.04.08 |
---|---|
Network Troubleshooting (0) | 2021.04.02 |
Worker Node Failure (0) | 2021.04.01 |
Control Plane Failure (0) | 2021.04.01 |
Application Failure (0) | 2021.04.01 |