Amazon web services 如果将kubeadm init与--cloud provider=aws标志一起使用，则kubernetes控制器管理器错误 k8s控制器管理器无法启动（通过更改AWS EC2标签解决）

我有类似的问题，因为这篇文章：，但这并没有提供任何解决问题的办法。下面是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

[Global]
KubernetesClusterTag=k8s
KubernetesClusterID=k8s

/etc/kubernetes/cloud config.conf

文件

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

[Global]
KubernetesClusterTag=k8s
KubernetesClusterID=k8s

解决方案 更改EC2实例标记，KEY=KubernetesCluster，VALUE=k8s（在我的例子中）。

kube dns总是挂起，因为weave-net崩溃 修复

cgroup

设置

• 将

  Environment=“KUBELET\u CGROUP\u 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并启动

根据

cloud config.conf

文件，键应该是

KubernetesCluster

，值应该是

k8s

。它应该是EC2角色，而不是IAM的用户。谢谢！更改标签解决了我的问题！一个新的问题是kube dns总是悬而未决。这可能是几件事，但您的网络是否正常运行（法兰绒、编织…）？您是否正确配置了sec组？我打开了连接到sec组的所有地址的所有端口，只是为了便于测试，所以我认为情况并非如此。我确实使用了weave net，它在我初始化后立即崩溃。我无法查看日志信息。我还尝试使用

kubectl descripe

，它没有提供有用的信息。