<p>I have two use cases where teams only want Pod A to end up on a Node where Pod B is running.  They often have many Copies of Pod B running on a Node, but they only want one copy of Pod A running on that same Node.  </p>

<p>Currently they are using daemonsets to manage Pod A, which is not effective because then Pod A ends up on a lot of nodes where Pod B is not running.  I would prefer not to restrict the nodes they can end up on with labels because that would limit the Node capacity for Pod B (ie- if we have 100 nodes and 20 are labeled, then Pod B's possible capacity is only 20).</p>

<p>In short, how can I ensure that one copy of Pod A runs on any Node with at least one copy of Pod B running?</p>

Howard_Roark
<p>The current scheduler doesn’t really have anything like this. You would need to write something yourself.</p>
