Topology For Volume Snapshots

[mdzraf]

Enhancement Description

• One-line enhancement description (can be used as a release note): Adding Topology Support For Volume Snapshots
• Kubernetes Enhancement Proposal: KEP-5943: Topology For Volume Snapshots #5944
• Discussion Link: 11/27/2025 Kubernetes CSI Implementation Meeting (see notes). No recording available.
• PRs by stage and milestone:
  • Alpha - v1.xx
    • KEP (k/enhancements) update PR(s):
    • KEP-5943: Topology For Volume Snapshots #5944
    • Code (k/k) update PR(s):
    • CSI Spec PR: KEP-5943: Introducing Snapshot Topology container-storage-interface/spec#606
    • External Snapshotter PR: Add snapshot topology support (KEP-5943) kubernetes-csi/external-snapshotter#1463
    • External Provisioner PR: Add snapshot topology support for Immediate binding (KEP-5943) kubernetes-csi/external-provisioner#1552
    • Scheduler Plugin PR: Adding SnapshotTopology Plugin (KEP-5943) kubernetes-sigs/scheduler-plugins#995
    • CSI-Test PR: Adding Changes for Snapshot Topology kubernetes-csi/csi-test#617
    • Docs (k/website) update PR(s):
    • [Draft] Introducing Topology For Volume Snapshots website#56208
    • Adding Entry For Snapshot Topology (Alpha KEP-5943) website#56679
    • CSI Doc: Adding Docs For Snapshot Topology (KEP-5943) kubernetes-csi/docs#645

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

[mdzraf]

/sig storage

[jsafrane]

I have another use case: a Kubernetes cluster on vSphere with multiple topologies (host groups, datacenters, ...) that do not have a shared storage. A snapshot of a volume is then usable only in the same topology as the original volume. It roughly corresponds to a multi-region cluster in a public cloud, however, the topologies in vSphere are usually "close" together, without any higher network delay.

[kannon92]

/assign @mdzraf