You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recommend setting a podAntiAffinity on Deployments and StatefulSets:
Either a preferredDuringSchedulingIgnoredDuringExecution or a requiredDuringSchedulingIgnoredDuringExecution anti affinity with the kubernetes.io/hostname key should be set.
Setting this prevents all pods in a deployment from being scheduled on the same node if there are other nodes available.
…me node
This check checks if Deployments and StatefulSets has a podAntiAffinity set with kubernetes.io/hostname as the topology key
This should help prevent scheduling pods on the same node, which can be a bad practice in case that node disappears (for whaterver reason)
This fixes#77
…me node
This check checks if Deployments and StatefulSets has a podAntiAffinity set with kubernetes.io/hostname as the topology key
This should help prevent scheduling pods on the same node, which can be a bad practice in case that node disappears (for whaterver reason)
This fixes#77
Recommend setting a podAntiAffinity on Deployments and StatefulSets:
Either a
preferredDuringSchedulingIgnoredDuringExecution
or arequiredDuringSchedulingIgnoredDuringExecution
anti affinity with thekubernetes.io/hostname
key should be set.Setting this prevents all pods in a deployment from being scheduled on the same node if there are other nodes available.
The text was updated successfully, but these errors were encountered: