Stay Out of My Yard! Isolation Segments - a New Feature for Isolating Workloads in Cloud Foundry
summary
Cloud Foundry 2.50+ adds compute Isolation Segments that administrators create with one POST request and populate by tagging Diego cells with a placement tag. Cells only host apps assigned to their segment, control plane remains shared, and developers use the same CF push workflow; entitlement plus setting a space or org default routes apps to the tagged cells. Demo verifies app IPs land on the expected cell. Current limits: isolation isn’t persisted on app records so queries are indirect, routing needs network setup, and log isolation is not implemented yet.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 0:30Agenda
- 1:14Why Isolation Segments
- 3:05Previous proposals
- 3:51Simplicity and flexibility
- 7:23Control planes with isolation segments
- 7:41Flexibility
- 11:00Groovy Animation
- 15:22Demo
- 17:13IP Addresses
- 17:55Create Organization
- 19:03Push Workload
- 21:24Creating Orgs
- 22:28Creating Isolation Segments
- 24:44App Stats
- 26:10Whats Next
- 29:46Questions
related talks
21mUpdate on Cloud Foundry Isolation Segments (formerly Elastic Clusters)
20mCompletely Isolate your App's Traffic: Isolation Segments at the Routing Tier
28mImmutability for PCF: Security in a Cloud Native World
35mResource Management Ecosystem and Cloud Foundry - A Review of the State of the Art
02mCloud Foundry
01h 25mWhat's New in CloudFoundry
29mMulti-DC Cloud Foundry: What, Why and How?
24mMicro-Segmentation's Impact on Cloud Environments