Mastering Modern Software Distribution: On-Prem, Air-Gapped, and BYOC Challenges
summary
Concrete steps and tools for shipping customer-managed software from build to deploy with examples: use release please plus conventional commits to auto-bump versions and generate release notes; produce SBOMs with Syft/anchore-style actions and attach them to OCI images; sign images via cosign using GitHub Actions OIDC; build true multi-arch images on native GitHub runners (CI time drops from 20+ minutes to ~5 minutes); publish Helm charts and images to a self-hosted OCI registry with download history and tag-restrictions for per-customer access; use SAF to bootstrap air-gapped clusters.
AI-written summary · about
chapters (15)
- 0:00Introduction and background
- 2:38Challenges of on-prem software
- 4:21Key considerations for deployment
- 5:43Semantic versioning explained
- 6:47Conventional commits and release notes
- 8:51Automating releases with Release Please
- 12:31Securing releases with SBOM and signing
- 16:46Signing images with Cosign
- 20:01Multi-architecture image support
- 22:36Deployment models overview
- 25:25Container registries for distribution
- 28:37Deployment agents and tools
- 30:03Air-gapped systems with Tufts
- 31:51Live demo introduction
- 39:52Q&A or AI debugging demo
related talks
23mMastering Secure Software Supply Chains
35mPractical Guides for Enhancing Your Software Supply Chain Security
47mBuilding Trust in Open Source: A Practical Guide to Securing Your ...
43mOur Dependence on Open Source Is Scary. SLSA, SBOM and Sigstore to the Rescue
46mA Security State of Mind: Continuous Security with Kubernetes
44mWhat does it take to deploy to production with confidence?
31mFast & Secure: Package, Sign, Verify, and Deploy
45mDeploying to production with confidence