← Monday, September 28, 2026Cloud & infraTool

Topograph publishes cluster topology for Kubernetes and Slurm schedulers

developer.nvidia.com by Elizabeth Goodman 12 min read Editor score 7/10

Topograph normalizes topology from cloud APIs and on-premises fabrics, then exposes it through Kubernetes labels, Slurm configuration, or Slinky ConfigMaps. Keeping scheduler topology current can help place AI workloads in efficient locality domains.

What
Topograph discovers cluster topology from cloud APIs or on-premises fabric systems and publishes it for workload managers.
How
It normalizes topology into a common model and exports Kubernetes node labels, Slurm configuration, or Slinky ConfigMaps.
Why it matters
Keeping schedulers current on GPU and fabric relationships helps place distributed workloads in locality domains and avoid cross-domain bottlenecks.
topology topology publishes publishes publishes cloud APIs on-premisesfabric systems Topograph Kubernetes nodelabels Slurmconfiguration SlinkyConfigMaps
Topograph turns discovered cluster topology into formats workload managers can use. Sketched from the article's own text.

Discussion

Discussion is not switched on yet. Use Note above to keep your own thoughts on this story.

Headline, summary, brief and diagram are written by a model from the source's own text; the link, byline and numbers come from the source. Read the original before relying on a claim.

Your note

Private to you. Stored in this browser, and synced to your account when you are signed in.