Right, so you’ve got Helm installed. You can run helm version without it throwing a fit. Congratulations, you now have a power tool with nothing to plug in. This is where Artifact Hub waltzes in, holding the extension cord. Think of it not as a chart repository, but as the public, searchable, sanity-checking index for pretty much every Helm chart you’ll ever need. It’s the replacement for the old Helm Charts repo, and it’s so much better it’s not even funny.

The old model was, frankly, a bit of a mess. You had one gigantic mono-repo where everyone dumped their charts. Finding anything was a chore, and versioning was a free-for-all. Artifact Hub is federated. It doesn’t host the charts itself; it’s an indexer. It points at thousands of separate repositories maintained by different projects and organizations, ingests their metadata, and provides a single, glorious place to search, discover, and vet them all. This is a vastly more scalable and sane approach.

Finding What You Actually Need

The primary interface is the website, artifacthub.io. Go there. Bookmark it. Your first instinct for any piece of software you want to run on Kubernetes should be to search for it here.

But let’s say you’re a terminal purist (I respect that). You can search right from the CLI. Want to find charts related to PostgreSQL?

helm search hub postgresql

This will spit out a list of charts from Artifact Hub, showing you the repository URL and a brief description. It’s useful, but the web UI is far more powerful for discovery because you can see screenshots, detailed documentation, security reports, and popularity metrics.

Now, finding a chart is one thing; choosing the right one is another. You’ll see twenty PostgreSQL charts. Which one do you use? Here’s my hierarchy of sanity:

  1. Official is best. The one labeled “PostgreSQL” by Bitnami is usually a safe, well-maintained, and brutally consistent bet. They are the de facto standard for public charts.
  2. The project’s own repo. Is there a chart in the actual postgresql project’s GitHub repo? Artifact Hub will often index it. This is a fantastic option if it exists.
  3. Be wary of random ones. That chart from some-random-username with 3 stars and last updated in 2019? Just keep scrolling.

Adding a Repository and Installing

You found a chart. Let’s use the Bitnami one as our example. The search result gives you a repo URL. To install from it, you first have to add that specific repository to your local Helm client.

helm repo add bitnami https://charts.bitnami.com/bitnami

This doesn’t download any charts. It just tells Helm, “Hey, you can find charts at this address.” The name bitnami is an alias you choose; you could call it banana if you wanted to, but for the love of all that is holy, use the standard name so you don’t confuse yourself later.

Now, update your local cache of what charts and versions are available in all your added repositories:

helm repo update

Seriously, do this often. It’s the equivalent of apt-get update. Now you can install PostgreSQL. But you’re not just going to run helm install my-postgres bitnami/postgresql, are you? Of course not. That would use all the default values, which is almost never what you want.

The Critical Step: Inspecting the Chart

This is the part everyone skips and then complains on Slack that their database has no password. Before you install anything, you must look at two things: the chart’s README on Artifact Hub and its default values.yaml.

First, get the chart’s values so you can see what knobs you can turn:

helm show values bitnami/postgresql > values.yaml

Now, open that values.yaml file. This is your launch configuration. It’s filled with commented-out goodness explaining every possible setting. You need to scan this. I need to set a password, maybe change the storage size, maybe enable metrics. I create a custom values file, say my-postgres-values.yaml, with just the overrides I need:

# my-postgres-values.yaml
auth:
  postgresPassword: "SuperSecretPassword123!" # Obviously, use a real password management strategy.
primary:
  persistence:
    size: 20Gi
metrics:
  enabled: true

Now you install. Helm will merge your overrides on top of the defaults.

helm install my-postgres bitnami/postgresgresql -f my-postgres-values.yaml

Why This Federation Thing Matters

The beauty of Artifact Hub’s model is trust and freshness. The Grafana team maintains their own chart repository. When they cut a new release, they push it to their repo. Artifact Hub almost immediately indexes it. You’re getting it straight from the source, not waiting for some central committee to approve a PR to a giant repo. This means faster updates, more ownership from the projects, and a clearer chain of custody. It’s just a better way to organize the world’s Helm charts.

So use it. Rely on it. But never trust a chart blindly. Always show values, always read the README, and for heaven’s sake, always check the container image tags it’s going to pull. Your cluster will thank you.