VKS on VCF 9.1 What Actually Changed & Why It Matters
A Comic Book Story in Seven Chapters
Issue #01 · May 2026 · The VCF 9.1 Saga
⚡ Cast of Characters ⚡
Captain VKS
vSphere Kubernetes Service 3.6
The hero. Born from vSphere, forged in CNCF conformance. Now powered up with VCF 9.1 abilities.
The Architect
Platform Engineer
Our protagonist. Runs multi-domain VCF estates. Needs Kubernetes at enterprise scale without the circus.
Cluster Creep
The Villain of Sprawl
Feeds on operational toil, slow provisioning, and fragmented toolchains. Grows stronger with every manual step.
The Oracle
VCF Operations 9.1
Sees all. Knows cost. Tracks every namespace. Speaks in metrics and FinOps.
🥊 The Challengers 🥊
The Cloud Twins
The Hyperscaler Duo
They move fast and always whisper: “Just move to our cloud.” They charge per hour and never let go.
The Red Baron
The Opinionated Platform
Arrives in full armor. Brings his own runtime, registry, mesh, and opinions about everything. Enterprise prices included.
The Wrangler
The Multi-Cluster Cowboy
Rides across any ranch — any cloud, any edge, any distro. Freedom is his creed. But who’s managing the cattle?
Bare Knuckle
The DIY Brawler
No platform. No hand-holding. Bare metal, kubeadm, and grit. Cheap up front. Costs you in blood and 3 AM pages.
Chapter 01The 37-Minute Nightmare
The data center. 6:42 AM. The Architect stares at a provisioning timer that refuses to move. Cluster Creep watches from the shadows, feeding on frustration.
The Architect
37 minutes to spin up a dev cluster. Thirty. Seven. Minutes. The hyperscaler team next door gets theirs in ten. The CTO is asking questions.
Cluster Creep
Yesss… and that’s just the deployment. Wait until you see the upgrade windows. I’ve got 45 minutes of downtime planned for each cluster. You have 200 clusters. Do the math. 😈
That’s 150 hours of maintenance windows per upgrade cycle… across the fleet…
May 5, 2026. Broadcom releases VCF 9.1. And everything changes.
Captain VKS
Miss me? I brought Fast Deploy. Let me show you the new numbers.
| Metric | VCF 9.0 | VCF 9.1 |
|---|---|---|
| Cluster Deploy Time | 37 min | 11 min (↓69%) |
| Cluster Upgrade Time | 45 min | 15 min (↓67%) |
| Max Clusters / Supervisor | ~100 | 500 |
| Node Pool Placement | Manual | DRS Intelligent |
Chapter 02The Challengers Step Forward
Word of VCF 9.1 spreads. Four challengers emerge from the fog, each claiming the throne of enterprise Kubernetes. The Architect has heard their pitches before.
The Cloud Twins
Adorable upgrade, Captain. But we’ve been doing sub-10-minute clusters for years. Managed control plane. Global regions. Auto-scaling node groups. Why fight gravity? Just come to the cloud.
Captain VKS
Sure — and your managed control plane costs how much per cluster per month? Multiply that by 500 clusters. Now add the egress fees. Now add the data sovereignty audit your CISO just mandated. I run on hardware you already own.
The Red Baron
How charming. You finally got CNI choice? I ship with my own SDN, my own service mesh, my own registry, my own CI/CD pipelines, and a full developer portal. I am the platform. You’re still assembling one.
Captain VKS
You are the platform. That’s the problem. Your opinions become my constraints. Your lifecycle becomes my upgrade treadmill. Your per-core subscription becomes my CFO’s nightmare. I give choice. You give mandates.
The Wrangler
Y’all are so cute with your single-vendor stacks. I run on any infrastructure. True multi-cluster freedom. No lock-in. Ever.
Captain VKS
Freedom is great until your team is maintaining six different infrastructure backends. I give you 500 clusters on one Supervisor with one operational model. You give them options and a prayer.
Bare Knuckle
I don’t need a platform. kubeadm, a Makefile, and raw skill. Zero licensing. Zero overhead. Pure Kubernetes.
Captain VKS
I respect the craft. But who patches your nodes at 2 AM? Who handles etcd backups? Who runs certificate rotation? Your “zero cost” platform costs three full-time engineers.
The Architect
I’ve evaluated all of you. Here’s my problem: I already run VCF. My VMs, NSX networking, vSAN storage, and security policies are all here. I need Kubernetes that joins my platform — not one that replaces it or ignores it.
The best Kubernetes platform is the one that doesn’t make me build a second operations team…
Chapter 03Fast Deploy — 11 Minutes or Bust
Captain VKS explains what changed under the hood. Fast Deploy isn’t a marketing stunt — it’s an architectural rework of the provisioning pipeline.
Captain VKS
Here’s what actually happened. We parallelized the node bootstrapping sequence, pre-staged container images into a local content library, and eliminated redundant API round-trips during cluster init. 11 minutes, from API call to workload-ready.
The Architect
What about upgrades? That’s where we bleed. Every cluster upgrade is a maintenance window, and my team juggles 200+ clusters.
Captain VKS
45 minutes down to 15. Pre-staged images, parallel node drain-and-replace, and Multiple Clusters per Zone means you keep workloads running on Zone A while upgrading Zone B.
⚡ IMPACT METER ⚡
The Cloud Twins
11 minutes… fine, that’s competitive. But can you match our global availability zones?
Captain VKS
I don’t need 60 regions. My Architect’s data stays in his sovereign data center, on his hardware, under his compliance umbrella. Your 60 regions are 60 places his CISO has to audit.
Chapter 04DRS Strikes Back — Intelligent Node Pool Placement
VCF 9.1 introduces Intelligent Node Pool Placement. This isn’t basic affinity rules — it’s DRS-level scheduling applied to Kubernetes node pools.
Captain VKS
GPU pods → GPU hosts. NVMe workloads → NVMe nodes. DRS algorithm decides placement — not your YAML-wrestling platform team.
The Red Baron
I have Topology Manager, NUMA-aware scheduling, and a full operator ecosystem. Infrastructure-aware placement is table stakes for me.
Captain VKS
You schedule within the cluster. I schedule the cluster itself. DRS sees the whole estate. Your scheduler sees one namespace.
The Oracle
With VKS Cost Showback in VCF Operations 9.1, I can tell you exactly what each namespace, each cluster, each team is costing you. FinOps FOCUS-compliant.
The Oracle
I also expose an API for your RAG pipelines and MCP frameworks — your AIOps engine can query cost data directly.
Per-NS
Cost Attribution
FOCUS
FinOps Compliant
Real-Time
Pricing Estimates
Show + Charge
Back Capability
Chapter 05Container-as-a-Service & The CNI Revolution
VCF 9.1 introduces a simplified Container Service — deploy containers without deep Kubernetes expertise. Meanwhile, VKS 3.6 opens up CNI choice for the first time.
Captain VKS
First: Container-as-a-Service. Your app teams get a self-service surface. Click, deploy, done. No Supervisor clusters or ClusterClass YAML.
Captain VKS
Second: CNI freedom. VKS 3.6 deprecated ClusterBootstrap. Pick your CNI through the Addon Framework using AddonConfig CRDs. Antrea default, but the door is open.
The Wrangler
Oh, you’re just now letting people choose their CNI? Welcome to 2022, Captain.
Captain VKS
You let them choose. I let them choose with validated blueprints, lifecycle support, and a single vendor to call at 3 AM. Choice without support is just risk with extra steps.
The Architect
And the Ingress story? The popular open-source Ingress controller is being retired…
Captain VKS
Avi Load Balancer — natively integrated. Centralized control plane, distributed data plane, full observability. Plus vDefend gives you zero-trust lateral security for every pod.
Chapter 06The Arena — Where Platforms Are Measured
The Architect pulls up the scoreboard. No hype. No marketing. Just the dimensions that matter when you’re running Kubernetes in a regulated enterprise with 500+ VMs already on VCF.
⚔️ HEAD TO HEAD ⚔️
| Dimension | 🛡️ Captain VKS | ☁️ Cloud Twins | 🎩 Red Baron | 🤠 Wrangler | 🥊 Bare Knuckle |
|---|---|---|---|---|---|
| Data Sovereignty | Your DC | Their DC | Your DC | Depends | Your DC |
| VM + K8s Unified Ops | Native | Separate | Separate | Separate | Separate |
| Infra-Aware Scheduling | DRS-Level | Node Groups | Topology Mgr | Manual | DIY |
| Cluster Scale Ceiling | 500 / Supervisor | Unlimited* | Per Infra | Per Infra | Per Team |
| Integrated FinOps | FOCUS Native | Cost Explorer | 3rd Party | 3rd Party | Spreadsheet |
| Network Security | vDefend + NSX | VPC / SG | Built-in SDN | BYO | BYO |
| Licensing Model | Per-Core VCF | Per-Cluster/Hr | Per-Core Sub | Open Source | Free |
| Day 2 Toil | Low | Low | Medium | Medium | High |
| AI / GPU Conformance | CNCF AI Cert | GPU Pools | Operators | BYO | BYO |
The Cloud TwinsWe still win on global reach and elastic scale.
The Red BaronAnd I still own the developer experience story. Integrated CI/CD, GitOps, developer portal — out of the box.
Captain VKS
Fair. I’m not claiming I win everywhere. But for organizations already running VCF — I’m the only Kubernetes that doesn’t create a second operational island. VMs and containers. One platform. One team. One pane.
The Architect
That’s the point everyone misses. I don’t need the “best” Kubernetes in a vacuum. I need the best Kubernetes for my stack. And my stack is VCF.
Chapter 07The Numbers Don’t Lie
💥 THE FINAL SHOWDOWN 💥
Broadcom surveyed 44 VCF 9 customers in March 2026. Here’s what they found — and why the challengers are looking over their shoulders.
51%
Less Infra Mgmt Time
46%
Less Monitoring Time
47%
Less Capacity Needed
39%
Faster MTTR/MTTI
Cluster Creep
No… NO! My sprawl… my complexity… my beautiful 37-minute deploy times… NOOOOO!
⚡ DEFEATED ⚡
The challengers watch from the sidelines. They’re not defeated — but they know the game just changed.
The Cloud TwinsWe’ll be back. Hybrid is where we’re heading too. See you at the edge…
The Red BaronImpressive numbers. But developer experience is the next battlefield. Don’t get comfortable.
The WranglerNot every ranch runs on one brand of fence. I’ll see you at the multi-cloud rodeo.
Bare KnuckleSome of us still prefer the raw fight. But… 11 minutes is hard to argue with.
The Architect
VCF 9.1 gives me 11-minute deploys, 15-minute upgrades, 500 clusters per Supervisor, intelligent DRS-based node placement, native FinOps cost tracking, self-service CaaS, open CNI choice, native Avi ingress, and zero-trust pod security. All on the same VCF stack I’m already running.
Captain VKS
And I’m CNCF Kubernetes AI Conformant. The challengers are strong — I respect each of them. But none of them can do what I do: run Kubernetes as a native citizen of your existing VMware estate.
VCF 9.1 doesn’t just iterate on VKS — it redefines the operational ceiling. Fast Deploy eliminates the provisioning tax. DRS-based placement removes manual scheduling toil. FinOps cost showback closes the last visibility gap. And with 500 clusters per Supervisor, VKS is the platform-scale Kubernetes runtime that VCF architects have been waiting for.
The challengers each bring real strengths — managed simplicity, opinionated platforms, multi-cloud freedom, zero-cost entry. This isn’t a story where the hero has no flaws. But for the Architect running a VCF estate with VMs, containers, and AI workloads under one roof — the calculus is clear.
The question is no longer “can VKS compete?” — it’s “what’s your excuse for not running it?”
The challengers each bring real strengths — managed simplicity, opinionated platforms, multi-cloud freedom, zero-cost entry. This isn’t a story where the hero has no flaws. But for the Architect running a VCF estate with VMs, containers, and AI workloads under one roof — the calculus is clear.
The question is no longer “can VKS compete?” — it’s “what’s your excuse for not running it?”
📚 Sources & References
- Deploy Modern Apps Faster with VKS in VCF 9.1 — VKS scale, Fast Deploy, CNI, node pool placement details
- Announcing VCF 9.1: Modern Private Cloud Built for Efficiency and Resilience — Product announcement, AI conformance, Container Service
- Scale, Simplify, and Secure Your Private Cloud Operations with VCF 9.1 — VCF Operations, VKS cost showback, FinOps FOCUS, customer survey data (n=44)
- Accelerate, Streamline, and Control Your Self-Service Private Cloud with VCF 9.1 — VCF Automation, Container Service runtime, Fast Deploy (37 min → 11 min)
- Simplify Workload Connectivity with VCF 9.1 — Multi-NIC VKS, Istio Service Mesh, Distributed Transit Gateway, IPFIX for pods
- Broadcom Press Release: VMware Cloud Foundation 9.1 — Official announcement, AI positioning, Private Cloud Outlook 2026 survey
- VKS 3.6 Release Notes — ClusterBootstrap deprecation, AddonConfig CRDs, ImageBaker, CNI flexibility
- VCF 9.1 Hands-on Labs — Now Live — Try VKS 3.6 scale, Fast Deploy, and multi-network in the lab
Leave a Reply