k8s学习_代码007(未授权)

本文介绍: 学习 ks8第一天开始部署的方式提示：以下是本篇文章正文内容，下面案例可供参考。

提示：这里可以添加本文要记录的大概内容：
学习 ks8第一天开始部署的方式

提示：以下是本篇文章正文内容，下面案例可供参考

sts“. This can take up to 4m0s
[kube let–check] Initial timeout of 40s passed.

    Unfortunately, an error has occurred:
            timed out waiting for the condition

    This error is likely caused by:
            - The kubelet is not running
            - The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)

    If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands:
            - 'systemctl status kubelet'
            - 'journalctl -xeu kubelet'

    Additionally, a control plane component may have crashed or exited when started by the container runtime.
    To troubleshoot, list all containers using your preferred container runtimes CLI.

    Here is one example how you may list all Kubernetes containers running in docker:
            - 'docker ps -a | grep kube | grep -v pause'
            Once you have found the failing container, you can inspect its logs with:
            - 'docker logs CONTAINERID'

error execution phase wait-control-plane: couldn’t initialize a Kubernet es cluster
To see the stack trace of this error execute with —v=5 or higher
[root@k8s-master ~]# kube adm config print init-defaults > init.default.yaml
W1128 13:29:56.206235 89761 config set.go:202] WARNING: kube adm cannot validate component configs for API groups [kubelet.config.k8s.io kubeproxy.config.k8s.io]
[root@k8s-master ~]# vi init.default.yaml
[root@k8s-master ~]# systemctl re start kubelet
[root@k8s-master ~]# kubeadm config images pull –config=init.default.yaml
W1128 13:30:23.803498 90232 configset.go:202] WARNING: kubeadm cannot val idate component configs for API groups [kubelet.config.k8s.io kubeproxy.config.k8s.io]
failed to pull image “k8s.gcr.io/kube-api server:v1.18.0”: output: Error response from daemon: Get https://k8s.gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
, error: exit status 1
To see the stack trace of this error execute with –v=5 or higher

[pref light] If you know what you are doing, you can make a check non–fatal with --ignore-preflight-errors=...
To see the stack trace of this error execute with –v=5 or higher
kubeadm reset