11-09, 20:15–20:35 (UTC), Room I
If you're managing cloud native applications, you already have a reliable, secured, performant container registry across your development to production environments. Where will you store your Helm charts, OPA Bundles, WASM, SBOMs, Scan Results, GitOps/RegOps and deployment artifacts? Do you really want to stand up and manage Yet Another Storage Solution (YASS)? Should you pull your developer focused Git infra into production? OCI Artifacts expands container registries to store any artifact. Artifacts are now adding Reference Types to store a graph of objects, including SBOMs, Signatures, Security Scan Results. We'll review the journey for OCI Artifacts and how you can build a new cloud native thing, without having to build and maintain YASS.
Steve is a PM Architect for Registries at Microsoft, an OCI TOB member and OCI Artifacts maintainer. Prior to joining Microsoft, Steve worked in software consulting and broadcast engineering, where he learned the balance of designing reliable, performant, available, secure and usable systems.
Steve can be found on Twitter @SteveLasker and his blog @ https://stevelasker.blog