DaemonSet不会创建任何Pod:v1.1.2 [英] DaemonSet doesn't create any pods: v1.1.2

问题描述

我正在尝试在6个节点的现有集群(已部署了多个容器)上启动DaemonSet.

I am attempting to launch a DaemonSet on an existing cluster of 6 nodes with multiple containers already deployed.

部署似乎成功了，但是没有创建Pod:

Deployment seems to succeed but no pods are created:

> ic describe ds
Name:       dd-agent
apiVersion: extensions/v1beta1
Image(s):   datadog/docker-dd-agent:kubernetes
Selector:   app=dd-agent,name=dd-agent,version=v1
Node-Selector:  <none>
Labels:     release=stable,tech=datadog,tier=backend
Desired Number of Nodes Scheduled: 0
Current Number of Nodes Scheduled: 0
Number of Nodes Misscheduled: 0
Pods Status:    0 Running / 0 Waiting / 0 Succeeded / 0 Failed
No events.
Setup

部署

AWS

我们正在运行使用kube-aws创建的示例集群 现有集群中有30个Pod已在6个节点上运行.

We are running the example cluster created with kube-aws The existing cluster has 30 pods already running across 6 nodes.

• CoreOS alpha(891.0.0)
• Kubernetes服务器v1.1.2
• 通过添加--runtime-config=extensions/v1beta1/daemonsets=true
更新了/etc/kubernetes/manifest/kube-apiserver.manifest以启用DaemonSet.

• CoreOS alpha (891.0.0)
• Kubernetes server v1.1.2
• Updated the /etc/kubernetes/manifest/kube-apiserver.manifest to enable DaemonSets by adding --runtime-config=extensions/v1beta1/daemonsets=true

在kube-aws-controller上，我使用以下命令重新启动了服务: sudo systemctl daemon-reload sudo systemctl restart kubelet

On the kube-aws-controller I restarted services with: sudo systemctl daemon-reload sudo systemctl restart kubelet

推荐答案

重新启动Kubelet不会重新启动由Kubelet管理的任何Pod.如果控制器管理器注意到在apiserver中启用了该功能，则仅会管理DaemonSet，因此您需要确保apiserver以该标志启动以启用alpha扩展，然后启动控制器管理器.

Restarting the Kubelet won't restart any of the pods being managed by the Kubelet. The controller manager will only manage DaemonSets if it notices that the feature is enabled in the apiserver, so you need to make sure that the apiserver is started with the flag to enable the alpha extensions and then start the controller manager.

这篇关于DaemonSet不会创建任何Pod:v1.1.2的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！