<p>Can I add some config so that my daemon pods start before other pods can be scheduled or nodes are designated as ready?</p>

<p>Adding post edit:</p>

<p>These are 2 different pods altogether, the daemonset is a downstream dependency to any pods that might get scheduled on the host. </p>

<p>There's no such a thing as <a href="https://kubernetes.io/docs/concepts/workloads/pods/pod-overview/" rel="nofollow noreferrer">Pod hierarchy</a> in Kubernetes between multiple separate types of pods. Meaning belonging to different Deployments, Statefulsets, Daemonsets, etc.  In other words, there is no notion of a master pod and children pods. If you like to create your custom hierarchy you can build your own tooling around, for example waiting for the status of all pods in a DaemonSet to start or create a new Pod or Kubernetes workload resource.</p>

<p>The closest in terms of pod dependency in K8s is <a href="https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/" rel="nofollow noreferrer">StatefulSets</a>.</p>

<p>As per the <a href="https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#deployment-and-scaling-guarantees" rel="nofollow noreferrer">docs</a>:</p>

<blockquote>
  <p>For a StatefulSet with N replicas, when Pods are being deployed, they are created sequentially, in order from {0..N-1}.</p>
</blockquote>
