ArtifactHub: We do not follow maps to buried treasure, and X never, ever marks the spot 🗺

Now that ArtifactHub is officially at 1.0.0, we thought it was time to take a deeper look at what it does, where it came from, and how we can use it. As many of you know, standardization around Kubernetes and the CNCF ecosystem is an ever-changing landscape, but let's try to figure out if we have found the holy grail of package management for k8s.

Issue #133

We are going to start with a high-level overview of package management in kubernetes itself. While Helm might not be your cup of tea, this is a great writeup of how and why you need package management; and shows a pretty straightforward way to do it. ☕️

This article introduces Artifact Hub and the motivations behind it. Ostensibly it is meant to be a unified package manager for all things CNCF; such as Falco, Helm and much more. As an added bonus it talks about its origins from KubeCon + CloudNativeCon in San Diego. 📦

Early validation for this project came in the form of Helm officially moving to Artifact Hub. This article breaks down the reasons why, and the plan moving forward. 🚛

Sticking with our Helm-heavy coverage we turn to this great tutorial that walks you through setting up your own charts and getting them on Artifact Hub. This one is a great primer to getting yourself going in the CNCF ecosystem with your own custom applications and charts.

One of the keys to proper package management is not being reliant on third parties for your deployment. This article from Artifact Hub's help section introduces you to running your own local copy and gets you one step closer to proper deployment techniques. 🔑

In this day and age, Security has to be a first class citizen – especially knowing where your images come from. Artifact Hub provides security scanning via Trivy so you can keep an eye on your software bill of materials. 👀

Register for the first in-person KubeCon in (nearly) two years!