Policy as [versioned] Code - you're doing it wrong
summary
Claim: treat policy as a versioned dependency, visible in a repo, testable and semantically versioned so you can push 10 updates in a single day and measure compliance across an org. Implementation: example GitHub org with policy v1.0.0 → v2.0.0 → v2.1.1, apps depending on specific versions, Renovate/Dependabot opening upgrade PRs, a small bash shim to evaluate against policy, Kind for CI, Kubernetes admission controllers accepting multiple versions. Result: it works end-to-end though some glue is brittle; visibility and automated PRs drive measurable compliance. policy as dependency semantic versioning
AI-written summary · about
chapters (6)
- 0:00Start
- 5:41Update policy... Daily!?
- 13:53open source?
- 15:49unit testing no really...
- 22:08k8s terraform
- 25:55Purposeless policy is potentially practically pointless policy.
related talks
40mPolicyfiles
18mTurning Policies, Standards, and Governance Into Enablers for Open-Source Innovation
36mThe future of dependency management, seen from 2022
11mPurpose Limitation with Policy Zones: What We Tried That Didn't Work
14mRisk Management in a Coded Enterprise
31mRenovate/Dependabot: How to Take Back Control of Dependency Updates
30mBreaking backwards compatibility: The easy way!
15mPutting the Semantics into Semantic Versioning