How DoD Uses K8s & Flux to Achieve Compliance & Deployment Consistency
summary
Kessel Run uses Kubernetes, Flux, GitLab pipelines, Terraform, Cluster API, Vault, Bitnami Sealed Secrets, Helm and Istio to automate cluster and app delivery across public cloud, on‑prem and air‑gapped networks. Flux enforces git as the single source of truth and rejects unsigned commits, Cluster API performs no‑downtime upgrades and autoscaling, and a RAD self‑service creates manifests that Flux applies. The result is audit‑able, versioned deployments that shrink ATO timelines from months to days or hours.
AI-written summary · about
chapters (8)
- 0:00Intro
- 1:43What is Castle Run
- 4:34Problem Space
- 11:47All Domain Common Platform
- 12:56Git Lab
- 15:10Deployment Example
- 17:43Baseline Services
- 20:50RAD
related talks
24mHosting Applications in the Real World
39mEnhance Your Kubernetes Experience with GitOps & Flux
36mCD and GitOps with flux @AdoreMe
47mOne Repo to Rule Them All: Kubernetes Cluster Tenancy with Flux v2
07mFluxCD - Gitops For All Sizes
01h 17mIntro to Kubernetes, GitOps, and Observability Hands-On Tutorial
42mIntro: Flux
23mGitOps: yea or nay?