Tips for centos to resolve startup problem (#4755)
* Tips for centos to resolve startup problem * Update document to diagnose centos setup problem * Update create-cluster-kubeadm.md
This commit is contained in:
@@ -559,6 +559,28 @@ Another workaround is to overwrite the default `kubeconfig` for the "admin" user
|
||||
sudo chown $(id -u):$(id -g) $HOME/.kube/config
|
||||
```
|
||||
|
||||
1. If you are using CentOS and encounter difficulty while setting up the master node:
|
||||
|
||||
Verify that your Docker cgroup driver matches the kubelet config:
|
||||
|
||||
```
|
||||
docker info |grep -i cgroup
|
||||
cat /etc/systemd/system/kubelet.service.d/10-kubeadm.conf
|
||||
```
|
||||
|
||||
If the Docker cgroup driver and the kubelet config don't match, change the kubelet config to match the Docker cgroup driver:
|
||||
|
||||
```
|
||||
update KUBELET_CGROUP_ARGS=--cgroup-driver=systemd to KUBELET_CGROUP_ARGS=--cgroup-driver=cgroupfs
|
||||
```
|
||||
|
||||
Then restart kubelet:
|
||||
|
||||
```
|
||||
systemctl daemon-reload
|
||||
service kubelet restart
|
||||
```
|
||||
|
||||
The `kubectl describe pod` or `kubectl logs` commands can help you diagnose errors. For example:
|
||||
|
||||
```bash
|
||||
@@ -569,5 +591,4 @@ kubectl -n ${NAMESPACE} logs ${POD_NAME} -c ${CONTAINER_NAME}
|
||||
|
||||
{% endcapture %}
|
||||
|
||||
|
||||
{% include templates/task.md %}
|
||||
|
||||
Reference in New Issue
Block a user