PodTopologySpread
E699814
PodTopologySpread is a Kubernetes feature that controls how pods are distributed across failure domains (such as nodes or zones) to improve availability and balance workloads.
All labels observed (1)
| Label | Occurrences |
|---|---|
| PodTopologySpread canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T7938912 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PodTopologySpread Context triple: [kube-scheduler, supports, PodTopologySpread]
-
A.
kube-scheduler
kube-scheduler is the Kubernetes control-plane service responsible for assigning newly created pods to suitable nodes based on resource availability, constraints, and scheduling policies.
-
B.
Kubernetes
Kubernetes is an open-source container orchestration platform that automates the deployment, scaling, and management of containerized applications across clusters of machines.
-
C.
Hydra Cluster
The Hydra Cluster is a massive galaxy cluster in the constellation Hydra, notable as one of the dominant structures within the nearby universe and a key component of the Hydra–Centaurus region.
-
D.
kube-proxy
kube-proxy is the Kubernetes network proxy that runs on each node to implement and manage virtual IPs and load-balanced access to services.
-
E.
kubelet
kubelet is the primary node-level agent in Kubernetes responsible for managing pods and their containers on each worker node.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: PodTopologySpread Target entity description: PodTopologySpread is a Kubernetes feature that controls how pods are distributed across failure domains (such as nodes or zones) to improve availability and balance workloads.
-
A.
kube-scheduler
kube-scheduler is the Kubernetes control-plane service responsible for assigning newly created pods to suitable nodes based on resource availability, constraints, and scheduling policies.
-
B.
Kubernetes
Kubernetes is an open-source container orchestration platform that automates the deployment, scaling, and management of containerized applications across clusters of machines.
-
C.
Hydra Cluster
The Hydra Cluster is a massive galaxy cluster in the constellation Hydra, notable as one of the dominant structures within the nearby universe and a key component of the Hydra–Centaurus region.
-
D.
kube-proxy
kube-proxy is the Kubernetes network proxy that runs on each node to implement and manage virtual IPs and load-balanced access to services.
-
E.
GKE on Bare Metal
GKE on Bare Metal is a Google Kubernetes Engine deployment option that lets you run and manage Kubernetes clusters directly on your own on‑premises bare metal infrastructure.
- F. None of above. chosen
Statements (50)
| Predicate | Object |
|---|---|
| instanceOf |
Kubernetes feature
ⓘ
pod scheduling policy ⓘ |
| affectedBy |
cluster topology labels
ⓘ
scheduler scoring and filtering logic ⓘ |
| aimsTo |
balance workloads across topology domains
ⓘ
improve workload availability ⓘ |
| appliesTo | pods selected by labelSelector ⓘ |
| canBeOverriddenBy | higher-priority scheduling constraints ⓘ |
| canBeUsedWith |
nodeAffinity
ⓘ
podAffinity ⓘ podAntiAffinity ⓘ |
| category | scheduling and topology management ⓘ |
| configuredAt | pod level ⓘ |
| configuredBy | topologySpreadConstraints field in PodSpec ⓘ |
| controls |
distribution of pods across failure domains
ⓘ
how pods are spread across nodes ⓘ how pods are spread across regions ⓘ how pods are spread across zones ⓘ |
| documentedIn | Kubernetes official documentation ⓘ |
| goal |
avoid concentration of replicas in a single zone
ⓘ
avoid concentration of replicas on a single node ⓘ |
| graduatedTo |
beta in Kubernetes 1.18
ⓘ
generally available in later Kubernetes versions ⓘ |
| hasProperty |
labelSelector
ⓘ
matchLabelKeys ⓘ maxSkew ⓘ minDomains ⓘ nodeAffinityPolicy ⓘ nodeTaintsPolicy ⓘ topologyKey ⓘ whenUnsatisfiable ⓘ |
| helpsWith |
balanced resource utilization across nodes
ⓘ
fault tolerance across failure domains ⓘ high availability of replicated workloads ⓘ |
| improvesOver | podAntiAffinity for even distribution use cases ⓘ |
| introducedIn | Kubernetes 1.16 as alpha feature ⓘ |
| relatedTo |
Kubernetes
ⓘ
Kubernetes scheduler ⓘ
linked to:
kube-scheduler
PodSpec ⓘ |
| replaces | legacy hard-coded default spreading logic ⓘ |
| requires | nodes labeled with appropriate topology keys ⓘ |
| scope | single Kubernetes cluster ⓘ |
| supportsPolicy |
DoNotSchedule whenUnsatisfiable policy
ⓘ
ScheduleAnyway whenUnsatisfiable policy ⓘ |
| usesConcept | topology spread constraints ⓘ |
| usesField |
pod.spec.topologySpreadConstraints
ⓘ
topologySpreadConstraints ⓘ |
| usesLabel |
kubernetes.io/hostname
ⓘ
topology.kubernetes.io/region ⓘ topology.kubernetes.io/zone ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: PodTopologySpread Description of subject: PodTopologySpread is a Kubernetes feature that controls how pods are distributed across failure domains (such as nodes or zones) to improve availability and balance workloads.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.