{"resourceId":"storagereview-portworx-kds-ga-prestaged-volumes-2026-11-10","versions":[{"version":"external-80a280bf217a26241dadd1a9f44b28258c82f99d6aaf91e303fbe89fad7ee077","resource":{"id":"storagereview-portworx-kds-ga-prestaged-volumes-2026-11-10","title":"Portworx Kube Datastore Reaches GA With Single-Replica Pools on FlashArray","organization":"StorageReview","sector":"Cross-sector; enterprise and public-sector storage buyers","geography":"Global","publishedAt":"November 10, 2026","publicationDate":"2026-11-10","eventDate":"2026-11-10","sourceName":"StorageReview","sourceLabel":"Independent trade press","sourceUrl":"https://www.storagereview.com/news/portworx-kube-datastore-ga-single-replica-pools-pre-staged-volumes","evidenceClass":"independent-reporting","outcomeClass":"emerging","topics":["infrastructure","governance-procurement"],"finding":"StorageReview (Harold Fritts, Nov 10, 2026) independently reports the same release: KDS is GA in Portworx Enterprise 3.7.2, using single-replica 'dynamic pools' on a shared array that leave data protection to the array, with FlashArray the only named backend. It relays Portworx's figure that shared-nothing replication carries roughly 2x-3x storage overhead and 3x-5x network I/O amplification, and notes Portworx has not published failover times. For AI, it describes pre-staged volumes as targeting inference start-up delays when tens to hundreds of gigabytes of model weights are re-downloaded after a pod moves, and states that Portworx expects the feature in Q1 2027, says scope and timing may change, and has not published startup-time figures.","sledRelevance":"Moderate: gives SLED buyers the questions the vendor post leaves open (one named backend, no failover or start-up numbers). Why now: same-day independent coverage of the Nov 10 KubeCon release, not previously archived.","evidence":"Trade-press reporting of vendor briefing with explicit notes on unpublished metrics; no testing.","architectureImplications":"Single-replica pools rely on the array for protection and move as a unit on node failure; pre-staged volumes tie inference pod placement to node-local copies.","governanceImplications":"Highlights that performance claims are unverified, which should feed procurement evaluation criteria.","securityPrivacyImplications":"Not addressed.","caveats":"Trade-press news write-up based on the vendor briefing; it adds scrutiny (missing figures, single named backend) but no independent testing. The 2x-3x and 3x-5x overhead figures are Portworx's, not measured by StorageReview. No public-sector content.","streamIds":["everpure"],"roles":{"sales":"Use this to set honest expectations. An independent outlet confirms KDS is GA but says Portworx named only FlashArray as a backend and published no failover or inference start-up figures. That supports a FlashArray-anchored VM-migration conversation, not a guaranteed AI performance pitch. Offer a measured pilot instead of quoting benefits.","engineering":"Key facts: KDS ships in Portworx Enterprise 3.7.2; dynamic pools hold replication-factor-one volumes and leave protection to the array; static pools remain for SharedV4 and replication-based needs. The 2x-3x storage and 3x-5x network overhead savings are Portworx's estimate. Design proofs should measure failover and pod time-to-ready directly.","delivery":"Interpretation: build test plans around the gaps this article names. Record failover time per pool move and inference pod start-up time before and after any change, and confirm backend support in writing. The platform team owns these measurements; procurement should hold benefit claims until they exist."},"roleDetails":{"sales":{"customerProblem":"Buyers cannot judge Portworx's efficiency and AI start-up benefits because the vendor has not published failover or start-up figures.","stakeholders":["Infrastructure manager","Procurement officer","Enterprise architect"],"discoveryQuestions":["Is your SAN a FlashArray, or another array Portworx has not listed?","What failover time does your VM workload require?","Would a measured pilot satisfy your evaluation committee?"],"valueHypothesis":"A FlashArray-backed estate may cut replica storage overhead; magnitude depends on current replication factor and is unmeasured independently.","potentialEngagement":"Measured pilot comparing KDS dynamic pools against current replication on a representative workload.","unsupportedClaims":["Vendor's 2x-3x / 3x-5x overhead figures as independent results","Any failover time","Any inference start-up improvement","Support for arrays other than FlashArray"]},"engineering":{"fit":"FlashArray customers running KubeVirt or OpenShift Virtualization with large persistent volumes.","architectureIntegration":"Dynamic pools (RF=1) on shared SAN with pool-level move on node failure; static pools for SharedV4 and replicated workloads.","prerequisites":["Portworx Enterprise 3.7.2","FlashArray backend","Workload classification by volume type"],"constraints":["SharedV4 volumes not eligible for dynamic pools","Only FlashArray named","No published failover times"],"security":"Data protection shifts to array features; confirm array snapshot and replication policies cover these volumes.","proofOfValue":["Node failure test measuring pool move time","Storage overhead before/after comparison","Inference pod time-to-ready test once pre-staged volumes ship"]},"delivery":{"work":"Validation test plan and evaluation scorecard for KDS and, later, pre-staged volumes.","dependencies":["Test cluster with FlashArray","Representative VM and inference workloads","Vendor support for 3.7.2"],"ownership":"Platform engineering, with procurement consuming the results.","skillsAdoption":"Teams need test-design and Kubernetes storage benchmarking skills.","governanceCheckpoints":["Test plan approval","Results review before procurement decision"],"acceptanceCriteria":["Proposed: failover time measured on at least three node-failure tests","Proposed: storage overhead change reported against current replication factor","Proposed: written confirmation of supported backends"],"risks":["Results not transferable from vendor lab","Feature scope change before GA","Benchmark design favoring vendor"]}},"retrievedAt":"2026-11-10T22:19:13-06:00","enrichedAt":"2026-11-10T22:20:58-06:00","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Not addressed.","procurementImplications":"Turn the article's open questions (backend list, failover, start-up time) into required evaluation criteria.","operatingModelImplications":"Array team and Kubernetes platform team share responsibility for protection under dynamic pools (interpretation).","sourceVerification":{"openedUrl":"https://www.storagereview.com/news/portworx-kube-datastore-ga-single-replica-pools-pre-staged-volumes","referenceExcerpt":"Portworx expects pre-staged volumes in Q1 2027, says scope and timing may change, and has not published startup-time figures.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}