<p>I am getting - when installing <a href="https://cilium.io" rel="nofollow noreferrer">Cilium</a>:</p>
<pre><code>Warning  FailedScheduling  4m21s (x17 over 84m)  default-scheduler  0/1 nodes are available: 1 node(s) didn't match pod anti-affinity rules. preemption: 0/1 nodes are available: 1 node(s) didn't match pod anti-affinity rules.
</code></pre>
<p>How can I see the rule and can I change it?</p>
<p>If I do <code>kubectl describe node</code>, id do not have anyy <code>nodeAffinity</code> settings. And the Node has <code>Taints:&lt;none&gt;</code></p>

<p>Run <code>$ kubectl get pods</code> , it shows Pending status. (<code>kubectl get pods -o wide</code>)</p>
<p>To describe the pod run <code>$ kubectl describe pod POD_NAME</code>, it shows a warning as part of events, if not works, try as suggested by @ <strong>Chris</strong> run <code>kubectl get pod &lt;name&gt; -o yaml</code>. There you'll find <code>spec.affinity</code>.</p>
<p>After identifying which anti-affinity rules triggers the warning. You can choose to</p>
<blockquote>
<p>either rectify the rule or make some changes in the cluster to support
the rule</p>
</blockquote>
<p><strong>For example :</strong> let's take a case, try to deploy 4 replicas of Ngnix deployment with <strong>podAntiAffinity</strong> rule in a 3 Node cluster. Here the last replica cannot be scheduled because no available Nodes left.</p>
<blockquote>
<p>You can choose to reduce the number of replicas, increase the number
of Nodes, adjust the rule to use soft/preference requirements or
remove the <strong>podAntiAffinity</strong> rule.</p>
</blockquote>
