How do you implement advanced scheduling in Kubernetes using node affinity, pod affinity, and taints/tolerations?

Kubernetes advanced scheduling provides fine-grained control over pod placement using multiple mechanisms for optimal resource utilization and application requirements.\n\nNode Affinity:\nConstrains pods to nodes with specific labels\n• requiredDuringSchedulingIgnoredDuringExecution: Hard requirement\n• preferredDuringSchedulingIgnoredDuringExecution: Soft preference\n• Supports complex label selectors\n• More expressive than nodeSelector\n\nPod Affinity/Anti-Affinity:\nSchedules pods relative to other pods\n• Affinity: Co-locate related pods\n• Anti-affinity: Spread pods across nodes/zones\n• Topology-aware scheduling\n• Supports namespaced and cluster-wide rules\n\nTaints and Tolerations:\nPrevent pods from scheduling on inappropriate nodes\n• Taints: Applied to nodes to repel pods\n• Tolerations: Applied to pods to tolerate taints\n• Effects: NoSchedule, PreferNoSchedule, NoExecute\n\nExample Advanced Scheduling:\nspec:\n affinity:\n nodeAffinity:\n requiredDuringSchedulingIgnoredDuringExecution:\n nodeSelectorTerms:\n - matchExpressions:\n - key: node-type\n operator: In\n values: ["compute-optimized"]\n podAntiAffinity:\n preferredDuringSchedulingIgnoredDuringExecution:\n - weight: 100\n podAffinityTerm:\n labelSelector:\n matchExpressions:\n - key: app\n operator: In\n values: ["web"]\n topologyKey: kubernetes.io/hostname\n tolerations:\n - key: "dedicated"\n operator: "Equal"\n value: "database"\n effect: "NoSchedule"\n\nBest Practices:\n• Use anti-affinity for high availability\n• Combine multiple scheduling constraints\n• Monitor scheduling decisions and latency\n• Test scheduling policies thoroughly\n• Use topology spread constraints for even distribution