如何在AWS EKS的Kubernetes集群上运行Tiller

时间:2019-02-15 13:13:22

标签: kubernetes amazon-eks

我用地形创建了EKS Kubernetes集群。一切正常,创建了群集,并且有一台EC2计算机。但是,我无法启动头盔并在其中安装Tiller。所有代码都在https://github.com/amorfis/aws-eks-terraform

如README.md中所述,在创建集群之后,我更新了~/.kube/config,创建了rbac,并尝试初始化helm。但是,它的pod仍在等待处理:

$> kubectl --namespace kube-system get pods
NAME                             READY   STATUS    RESTARTS   AGE
coredns-7554568866-8mnsm         0/1     Pending   0          3h
coredns-7554568866-mng65         0/1     Pending   0          3h
tiller-deploy-77c96688d7-87rb8   0/1     Pending   0          1h

以及其他2个coredns吊舱。

我想念什么?

更新:describe的输出:

$> kubectl describe pod tiller-deploy-77c96688d7-87rb8 --namespace kube-system
Name:               tiller-deploy-77c96688d7-87rb8
Namespace:          kube-system
Priority:           0
PriorityClassName:  <none>
Node:               <none>
Labels:             app=helm
                    name=tiller
                    pod-template-hash=3375224483
Annotations:        <none>
Status:             Pending
IP:
Controlled By:      ReplicaSet/tiller-deploy-77c96688d7
Containers:
  tiller:
    Image:       gcr.io/kubernetes-helm/tiller:v2.12.2
    Ports:       44134/TCP, 44135/TCP
    Host Ports:  0/TCP, 0/TCP
    Liveness:    http-get http://:44135/liveness delay=1s timeout=1s period=10s #success=1 #failure=3
    Readiness:   http-get http://:44135/readiness delay=1s timeout=1s period=10s #success=1 #failure=3
    Environment:
      TILLER_NAMESPACE:    kube-system
      TILLER_HISTORY_MAX:  0
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from tiller-token-b9x6d (ro)
Conditions:
  Type           Status
  PodScheduled   False
Volumes:
  tiller-token-b9x6d:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  tiller-token-b9x6d
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:          <none>

1 个答案:

答案 0 :(得分:1)

尝试允许主服务器运行Pod 根据此问题issue form githup

kubectl taint nodes --all node-role.kubernetes.io/master-