Uploaded April 2026 | Updated September 2026, 4 hours ago
Keith Lee walks through cf push on Tanzu Platform - the one command that takes source code from your laptop to a running, health-checked, route-registered, observable app in seconds.
The scenario: a developer on a polyglot microservices app (Acme Fitness) working on the catalog service. The catalog is empty, code needs to ship. One cf push later, the platform:
- Uploads the source to the blob store
- Detects the runtime (Java, Node, Python, or .NET)
- Stages the app: downloads the runtime, installs dependencies, compiles, and packages everything into a droplet
- Schedules container instances across available resources
- Spins up containers with the right memory and disk limits
- Downloads the droplet, starts the app, runs health checks
- Registers routes so traffic flows to the new app
That's the same pipeline a typical CI/CD setup builds out manually across a dozen tools and YAML files. cf push does it as one command.
The demo also covers binding a Postgres service from the Tanzu marketplace (credentials auto-injected, no secret juggling), and the observability story once the app is running: RED metrics, JVM metrics, resource usage, log search and analytics, and the platform's built-in recommendations for performance, security, compliance, and dependency freshness.
Narrated by Keith Lee.
Interested in a platform that can help you with enterprise-y excellence? Check it out: vmware.com/products/app-platform/tanzu
Index:
00:00 Developer working on the Acme Fitness catalog service
00:13 `cf push` - one command
00:17 What cf push actually does (upload, runtime detection, staging)
00:33 Droplet packaging, container scheduling, health checks, routes
01:02 cf push vs a manual CI/CD pipeline
01:12 Self-service marketplace: creating a Postgres instance
01:34 Binding Postgres to the app (auto-injected credentials)
01:43 Working catalog, app running
01:48 Tanzu Platform insights and topology
01:58 RED metrics, JVM metrics, resource usage, logs
02:12 Recommendations: performance, security, compliance, library age
02:28 Service-level telemetry for bound services
Keith Lee walks through cf push on Tanzu Platform - the one command that takes source code from your laptop to a running, health-checked, route-registered, observable app in seconds.
The scenario: a developer on a polyglot microservices app (Acme Fitness) working on the catalog service. The catalog is empty, code needs to ship. One cf push later, the platform:
- Uploads the source to the blob store
- Detects the runtime (Java, Node, Python, or .NET)
- Stages the app: downloads the runtime, installs dependencies, compiles, and packages everything into a droplet
- Schedules container instances across available resources
- Spins up containers with the right memory and disk limits
- Downloads the droplet, starts the app, runs health checks
- Registers routes so traffic flows to the new app
That's the same pipeline a typical CI/CD setup builds out manually across a dozen tools and YAML files. cf push does it as one command.
The demo also covers binding a Postgres service from the Tanzu marketplace (credentials auto-injected, no secret juggling), and the observability story once the app is running: RED metrics, JVM metrics, resource usage, log search and analytics, and the platform's built-in recommendations for performance, security, compliance, and dependency freshness.
Narrated by Keith Lee.
Interested in a platform that can help you with enterprise-y excellence? Check it out: vmware.com/products/app-platform/tanzu
Index:
00:00 Developer working on the Acme Fitness catalog service
00:13 `cf push` - one command
00:17 What cf push actually does (upload, runtime detection, staging)
00:33 Droplet packaging, container scheduling, health checks, routes
01:02 cf push vs a manual CI/CD pipeline
01:12 Self-service marketplace: creating a Postgres instance
01:34 Binding Postgres to the app (auto-injected credentials)
01:43 Working catalog, app running
01:48 Tanzu Platform insights and topology
01:58 RED metrics, JVM metrics, resource usage, logs
02:12 Recommendations: performance, security, compliance, library age
02:28 Service-level telemetry for bound services
