VMware by Broadcom · Software · YoctoIT tech page

Tanzu

VCF's application layer: integrated Kubernetes and a developer platform inside the infrastructure you already have.

FOCUS · K8S INSIDE VCFThe containers next to the VMs: the platform's Kubernetes, without DIY clusters
Request the Free Assessment Learn more
YoctoIT material for clients and partners · VMware, vSphere, vSAN, NSX and the other products mentioned are trademarks of Broadcom Inc.
01 · What it is

Tanzu Platform, made clear.

Tanzu (with vSphere Kubernetes Service) integrates Kubernetes into VCF: the clusters are born from the platform with NSX network and vSAN storage already connected, they're managed with the stack's lifecycle, and the Tanzu Platform adds the developer experience — build, deploy and data services — on top. Enterprise K8s without the far west of artisanal clusters.

VKS
the platform's native K8s clusters: born already integrated
One lifecycle
containers and VMs updated by the same VCF process
Dev experience
build and deploy for the developers: the platform, not just the cluster
Tanzu Platform
OFFICIAL VMWARE BRANDING · TANZU
CONSOLE REALE · TANZU HUB · FONTE: VMWARE BLOG
REAL CONSOLE · TANZU HUB · SOURCE: VMWARE BLOG
02 · How to use it well

The things that make the difference.

The integration

Apps: microservices & modernthe new that's coming
VKS · K8s clusters
NSX · network
vSAN · storage
integrated by birth
Tanzu Platformthe DX on top of the clusters
VCF · the platforma single stack to govern
VMs and containers, one home

Clusters with rules

Namespaces, quotas and policies per team: multi-tenancy thought out before the first pod.

The network already right

NSX for ingress and network policies: microsegmentation on the containers too.

Registry and supply chain

Harbor and signed images: the software that enters is tracked.

The honest comparison

VKS vs OpenShift vs cloud: the K8s choice on YOUR context — we make it with facts.

03 · In depth

The Kubernetes runtime and the platform experience

Tanzu brings the containers onto VCF: the vSphere Kubernetes Service (VKS) creates upstream-conformant clusters directly from vSphere (the nodes are VMs managed by the Supervisor), the vm classes and storage classes reuse the platform's resources and policies; Tanzu Platform adds the developer experience (build service with buildpacks, application spaces, services marketplace); the network is NSX or Antrea, the registry is Harbor.

  • Supervisor — vSphere that speaks Kubernetes: the clusters as platform objects
  • VKS conformant — certified upstream: no fork, the apps portable
  • vm class — the node sizes from policy: the K8s cluster with vSphere governance
  • Harbor — the enterprise registry with scanning and replication
  • Antrea/NSX — the integrated network policy: the pods in the security model
  • Build service — from code to image with buildpacks: the Dockerfile optional
04 · Numbers and lifecycle

The numbers that matter.

min
the K8s cluster provisioned by the Supervisor
100%
CNCF conformant: portability guaranteed
1
one platform for VMs and containers: skills and licenses reused
GitOps
declarative deployment as standard
In-house K8s pays off on the existing: Supervisor, classes and governance activated by us — the containers without one more platform.
05 · Use cases

Where it really pays off.

Gradual modernization

The new apps in containers, next to the usual VMs.

Internal platforms

K8s as-a-service for the development teams.

Cluster consolidation

The artisanal clusters brought back into the platform.

Serious Kubernetes is integrated, not propped up: inside VCF it's born already connected — we govern it.