What are Extended Toleration Operators in Kubernetes v1.35?

Alpha feature adding Gt and Lt to tolerations for numeric taints. Enables threshold scheduling like "failure <5%".

How do Gt and Lt toleration operators work?

Gt matches if taint value > toleration value (e.g., tolerates high-perf nodes). Lt opposite. Works with NoSchedule, NoExecute, PreferNoSchedule.

Will Kubernetes numeric tolerations replace NodeAffinity?

No—complements it. Tolerations add eviction and safer defaults. Use both for hybrid setups.

🏗️ DevOps & Infrastructure

Kubernetes 1.35: Numeric Taints Finally Tame Spot Node Chaos

Q: How do Gt and Lt toleration operators work?

Gt matches if taint value > toleration value (e.g., tolerates high-perf nodes). Lt opposite. Works with NoSchedule, NoExecute, PreferNoSchedule.

Spot instances promise 90% cost cuts in Kubernetes clusters. But until v1.35's numeric tolerations, you're stuck with crude hacks. Time to get precise.

theAIcatchup Apr 07, 2026 3 min read

Kubernetes nodes with numeric taint icons balancing spot and on-demand pools

⚡ Key Takeaways

Kubernetes v1.35's Gt/Lt operators enable numeric thresholds in tolerations, fixing spot node scheduling woes. 𝕏
Taints provide safer defaults and evictions vs. NodeAffinity's preferences. 𝕏
Alpha feature poised for fast graduation amid 90% spot savings pressure. 𝕏

Published by

theAIcatchup

Community-driven. Code-first.

#Cluster Scheduling #scheduling operators #taints and tolerations

Worth sharing?

Get the best Open Source stories of the week in your inbox — no noise, no spam.

Originally reported by Kubernetes Blog

⚡ Key Takeaways

The 60-Second TL;DR

theAIcatchup

Share this article

Worth sharing?

Related Stories

Kubernetes Just Killed Ingress NGINX: Half Your Clusters Are Suddenly Vulnerable

Uptrack Ditches Databases for Pure BEAM Consensus — And It Actually Works

CI/CD Pipelines: Automating Software's Beating Heart

Kubernetes Pods Stuck in Pending? The Placeholder Trick That Slashes Scale Times by Minutes

Stay in the loop