Bringing Shipwright to Beta - and Beyond!
summary
Shipwright announces beta API v0.12 that stabilizes the core: the build strategy stays separate from build definition, the API enforces single Source per build and opinionated clone steps, and tool-specific fields are removed to stay tool-agnostic (Docker, Buildpacks, Kaniko, jib, etc.). The beta requires declaring a pod security context in build strategies to reduce privileged/root usage. Alpha APIs are phased out, integrations with Kubernetes/Tekton continue, and image supply-chain outputs (SBOMs, signatures, provenance) are prioritized with existing Trivy work.
AI-written summary · about
chapters (6)
related talks
33mProject Shipwright: Build Container Images on k8s
20mDevSecOps with Shipwright and Tekton
40mPlatform SIG
27mMike McQuaid at StaffPlus london 2023
24mBuild Your Own Shipyard
26mLeveraging SBOMS to Automate Packaging, Transfer, and Reporting of D...
49mDeploying to production with confidence
01h 12mHow to release open source library in 2020
