All Apps in Practice

VCF Automation All Apps, used for real rather than read about. One VKS cluster built two ways, then a whole demo stack from a single request. Handy if you know kubectl and want to see what the catalog adds, or the other way round. Start with One VKS cluster, two ways.

Seven demo apps behind seven VIPs on one VCFA-deployed VKS cluster

Seven demo apps, one request: deploying a showcase stack via VCF Automation

Seven demo apps, Pac-Man and KubeDoom among them, on a VKS cluster that VCF Automation built in a tenant VPC, each with its own NSX virtual IP. The proper tenanted path, what you get for free, and the traps.

The same Cluster manifest applied by kubectl and requested through the catalog — and what the second path adds for free

One VKS cluster, two ways: kubectl vs VCF Automation All Apps

The same VKS cluster built twice: once with kubectl, once as a VCF Automation request. The Cluster object is identical. Everything around it isn’t, and the difference is what you get for free.