Container Factory for Aerospace & Defense Enterprises
summary
Collins Aerospace builds a self‑service "container factory" that produces declarative ephemeral build environments so legacy avionics code (Borland C++, GCC49, Windows 95-era artifacts) can be rebuilt, tested and archived without long‑lived lab servers. Pipelines use hadolint, grype and trivy for dual scanning, GitLab for CI, Ansible/EC2 for builds, and zarf from Defense Unicorns to declare artifacts; containers get signatures, immutable audit records (retained 99 years) and automated revocation by cluster. The system is working but struggles with shadow IT, policy misalignment and real‑time priority/privilege requirements.
AI-written summary · about
chapters (8)
- 0:00Start
- 1:11THE PROBLEM
- 5:01CONTAINER STACK
- 9:42DEVELOPER EXPERIENCE
- 11:37DEVELOPMENT WORKFLOW
- 12:57BUILD PIPELINE
- 16:31RELEASE PIPELINE
- 16:56POST PIPELINE
related talks
27mAutomating the DoD Container Hardening Pipeline
52mContinuous Delivery with Containers: The Good, the Bad, and the Ugly
36mContainer Security Made Easy – Tools and Techniques for Developers
33mDevSecOps, Containers & Shift-Left: Are Those Just Buzzwords?
26mCyber Engineering with Containers
25mCloud Native Deployments in Air Gapped Environments
48mSecurity and compliance for container-based microservices
35mSecuring the Perimeter - CFCR/CFAR Chain of Custody With CI/CD Pipelines