CODEWITHSUNDEEP
kubernetes
c1freitas
c1freitas

Reputation: 146

DaemonSet doesn't create any pods: v1.1.2

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

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

Deployment

AWS

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

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

Upvotes: 0

Views: 3305

Answers (1)

Robert Bailey
Robert Bailey

Reputation: 18200

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.

Upvotes: 3

Related Questions