<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Affinity on Support Tools</title><link>https://support.tools/tags/affinity/</link><description>Recent content in Affinity on Support Tools</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 20 Aug 2024 21:00:00 -0500</lastBuildDate><atom:link href="https://support.tools/tags/affinity/index.xml" rel="self" type="application/rss+xml"/><item><title>Why Broken Pod Affinity/Anti-Affinity Rules Can Disrupt Your Kubernetes Deployments</title><link>https://support.tools/broken-pod-affinity-rules/</link><pubDate>Tue, 20 Aug 2024 21:00:00 -0500</pubDate><guid>https://support.tools/broken-pod-affinity-rules/</guid><description>&lt;p&gt;Pod affinity and anti-affinity rules allow you to instruct Kubernetes which Node is the best match for new Pods. Rules can be conditioned on Node-level characteristics such as labels, or characteristics of the other Pods already running on the Node.&lt;/p&gt;&#10;&lt;p&gt;Affinity rules attract Pods to Nodes, making it more likely that a Pod will schedule to a particular Node, whereas anti-affinity has a repelling effect which reduces the probability of scheduling. Kubernetes evaluates the Pod’s affinity rules for each of the possible Nodes that could be used for scheduling, then selects the most suitable one.&lt;/p&gt;&#10;&lt;p&gt;The affinity system is capable of supporting complex scheduling behavior, but it’s also easy to misconfigure affinity rules. When this happens, Pods will unexpectedly schedule to incorrect Nodes, or refuse to schedule at all. Inspect affinity rules for contradictions and impossible selectors, such as labels which no Nodes possess.&lt;/p&gt;</description></item></channel></rss>