Carvel and Bosh, a Match Made in Heaven?
summary
Shows how to take Carvel bundles, relocate all images with image-package/imgpkg, and pack their blobs into a BOSH release so Kubernetes tooling can run in an air‑gapped site. Uses k3s via BOSH, the docker-distribution registry BOSH release, ytt and kapp/controller tooling, and a package repository manifest; builds a local registry, copies blobs into BOSH release blobs, deploys kapp-controller and then a package-install CRD to install the app. Demo mostly works but DNS flakiness and a window where old images are briefly unavailable require extra copy/cleanup steps.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:25Carvel tools overview
- 3:34Setting up local registry
- 6:04Relocating images with imgpkg
- 9:28Creating BOSH release
- 12:23Installing kapp-controller
- 16:15Deploying package with kapp
- 17:59Future improvements
- 18:49Q&A
related talks
06mYou mean I don't have to write a BOSH release?
36mClosing the Developer Experience Gap of your Container Platforms
13mAuthoring a BOSH Release Is Actually Easy!
39mManaged CF-as-a-Service: An Operator's Cookbook
41mAbstractions on Abstractions, Are You Building for Kubernetes?
36mKubo - Your Gateway Drug to Cloud-Native - Cornelia Davis, Pivotal
33mDocker and Cloud Foundry: The 3 Use Cases
01h 02mCloudFoundry or Kubernetes/Kubo: Choosing the Right Platform for the Job