/kind bug
/sig scheduling
related to #59194

When the ScheduleDaemonSetPods alpha feature is enabled, the daemonset controller creates pods with affinity terms that depend on the kubernetes.io/hostname label on a Node being equal to the node name.

That is not a valid assumption. Node name and hostname are distinct and are definitively known to be different in some clusters.

If the DaemonSet wants to use scheduling to assign pods to nodes, it must do so with a scheduling predicate that deterministically resolves to the desired node and only the desired node (e.g. not a label that could match nodes other than the desired node)