如果在--cloud-provider = aws標志中使用kubeadm init，則kubernetes控制器管理器錯誤

Question

k8s控制器管理器無法啟動（通過更改AWS EC2標簽解決）

我有與此帖子類似的問題： kubeadm使用“ cloud-provider = aws”時 ， kube-controller-manager不會啟動 ，但這並沒有提供解決此問題的任何解決方案。 以下是kubernetes控制器管理器的日志統計信息。

I0705 17:59:05.941049       1 controllermanager.go:116] Version: v1.10.3
W0705 17:59:05.941983       1 authentication.go:55] Authentication is disabled
I0705 17:59:05.942004       1 insecure_serving.go:44] Serving insecurely on 127.0.0.1:10252
I0705 17:59:05.942450       1 leaderelection.go:175] attempting to acquire leader lease  kube-system/kube-controller-manager...
I0705 17:59:22.823671       1 leaderelection.go:184] successfully acquired lease kube-system/kube-controller-manager
I0705 17:59:22.823945       1 event.go:218] Event(v1.ObjectReference{Kind:"Endpoints", Namespace:"kube-system", Name:"kube-controller-manager", UID:"ec7f1208-807c-11e8-bc66-0e594759e784", APIVersion:"v1", ResourceVersion:"289", FieldPath:""}): type: 'Normal' reason: 'LeaderElection' k8s_1bbcc7bc-807d-11e8-859d-0e594759e784 became leader
I0705 17:59:22.849017       1 aws.go:1026] Building AWS cloudprovider
I0705 17:59:22.849064       1 aws.go:988] Zone not specified in configuration file; querying AWS metadata service
F0705 17:59:22.851606       1 controllermanager.go:159] error building controller context: cloud provider could not be initialized: could not init cloud provider "aws": error finding instance i-07df027cffda674bc: "error listing AWS instances: \"NoCredentialProviders: no valid providers in chain. Deprecated.\\n\\tFor verbose messaging see aws.Config.CredentialsChainVerboseErrors\""

/etc/kubernetes/aws.conf文件。

apiVersion: kubeadm.k8s.io/v1alpha1
kind: MasterConfiguration
cloudProvider: aws
kubernetesVersion: 1.10.3

/etc/kubernetes/cloud-config.conf文件。

[Global]
KubernetesClusterTag=k8s
KubernetesClusterID=k8s

解

更改EC2實例標簽，KEY = KubernetesCluster ，VALUE = k8s （在我的情況下）。

Answer 1

由於編織網絡崩潰，kube-dns始終處於等待狀態

修復cgroups設置。

• 將Environment="KUBELET_CGROUP_ARGS=--cgroup-driver=cgroupfs"到/etc/systemd/system/kubelet.service.d/10-kubeadm.conf 。
• 重新啟動kubelet服務。

   sudo systemctl deamon-reload sudo systemctl restart kubelet 

在創建kubernetes集群之前安裝weave net並啟動。