IPv6 in Cloud Foundry - Status Update
summary
Status update shows dual stack Ingress on AWS works and a clear migration path using proxy protocol to retain client IPs; testing starts for SAP services on Cloud Foundry and AWS. BOSH needs CPI and stemcell changes to instantiate IPv6 addresses and BOSH director and agents are single-stack today. Container runtime progress: runC supports IPv6, Garden lacks IPv6 so a proof of concept is underway; Silktalk (Silk) currently blocks dual stack and needs either extension or replacement.
AI-written summary · about
chapters (5)
- 0:00Introduction and status
- 1:02Dual stack Ingress on AWS
- 3:51BOSH and container runtime
- 7:52Hyperscaler support comparison
- 9:20Next steps and call to action
related talks
21mThe Way to Cloud Foundry with IPv4+IPv6 Dual Stack at SAP
32mIPv6 / Dual-Stack in Kubernetes - Why, When, Where and How?
30mLiberate Your Cloud Foundry Installation From Being Constrained to a Single Cloud
17mThe Long Road to IPv4/IPv6 Dual-stack Kubernetes
26mIPv6 First, Not Just Ready: Kubernetes Without IPv4 Using Cilium
32mCF Networking: All Your Packets are Belong to Us
30mExtending the Reach of Cloud Foundry: A New Stack and Supported OS
28mManaging Multiple Clouds with a Single BOSH Deployment