Uploaded July 2026 | Updated September 2026, 3 hours ago
@OrenPenso goes over how Tanzu Platform works with Kubernetes. (1) Tanzu Platform runs its own Kubernetes cluster, managed end to end, so nobody on your team needs to maintain the Kubernetes layer under your services. (2) If you want a cluster of your own you make a VKS cluster outside the platform and do whatever you like with it. (3) And if you’ve got workloads already running on Kubernetes and you want them talking to services on the platform, there’s an operator for that, so you don’t have to move anything.
Cloud Foundry is still the backend runtime. Kubernetes is added alongside it, and from a developer’s side you just create a service and the platform decides where it lands.
See the full talk: youtube.com/watch?v=wSiPdlqORyg
The operator he describes ships as Connected Clusters: techdocs.broadcom.com/us/en/vmware-tanzu/platform/tanzu-hub/10-4/tnz-hub/connected-clusters-overview.html
And if you’d like to try it: vmware.com/products/app-platform/tanzu
@OrenPenso goes over how Tanzu Platform works with Kubernetes. (1) Tanzu Platform runs its own Kubernetes cluster, managed end to end, so nobody on your team needs to maintain the Kubernetes layer under your services. (2) If you want a cluster of your own you make a VKS cluster outside the platform and do whatever you like with it. (3) And if you’ve got workloads already running on Kubernetes and you want them talking to services on the platform, there’s an operator for that, so you don’t have to move anything.
Cloud Foundry is still the backend runtime. Kubernetes is added alongside it, and from a developer’s side you just create a service and the platform decides where it lands.
See the full talk: youtube.com/watch?v=wSiPdlqORyg
The operator he describes ships as Connected Clusters: techdocs.broadcom.com/us/en/vmware-tanzu/platform/tanzu-hub/10-4/tnz-hub/connected-clusters-overview.html
And if you’d like to try it: vmware.com/products/app-platform/tanzu
