Hosting a Chart Repository
Serving charts over HTTP or object storage.
Hosting a Chart Repository is a free Helm Academy lesson on CoddyKit — lesson 3 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Helm Academy learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.
Serving Charts to Others
Once you have archives and an index.yaml, hosting a repo means making those files reachable over HTTP. Helm just needs to download them.
Any Static Host Works
A Helm repo has no server-side logic. Any plain static file server that returns your .tgz files and index.yaml is a valid repository.
Object Storage Is Popular
Teams often park charts in a bucket like S3 or Google Cloud Storage. Public read access turns the bucket into a working chart repo.
GitHub Pages as a Repo
A free favorite is GitHub Pages. Commit your .tgz files and index.yaml to a branch, enable Pages, and you have a hosted repo.
The URL Must Match
The address you serve from has to equal the --url you baked into index.yaml. A mismatch makes downloads fail with 404 errors.
helm repo index ./dist --url https://you.github.io/chartsUsers Add Your Repo
Consumers register your repo with helm repo add, giving it a local nickname pointed at your served URL.
helm repo add acme https://charts.example.comThen They Update and Search
After adding, users run helm repo update to fetch your index, then helm search repo to discover the charts you publish.
helm repo update
helm search repo acmeInstalling From Your Repo
Installing uses the repo/chart shorthand. Helm reads the cached index, downloads the right .tgz from your host, and deploys it.
helm install web acme/mychartChartMuseum for Dynamic Repos
If you want uploads via API instead of manual commits, ChartMuseum is an open-source server that stores charts and rebuilds the index for you.
Serve Over HTTPS
Always host charts over HTTPS. It stops tampering in transit and many setups expect a secure URL when adding the repo.
Keep Old Versions Online
Never delete a published .tgz still listed in your index. Existing installs and rollbacks rely on that exact archive staying downloadable.
Quick Check
A teammate ran helm repo add but installs return 404 for the .tgz. What is the likely cause?
Recap: Hosting a Repo
You learned a Helm repo is just static files served over HTTPS, with the served URL matching index.yaml. Users add, update, and install from it. 🌐
Frequently asked questions
Is the “Hosting a Chart Repository” lesson free?
Yes — the full text of “Hosting a Chart Repository” is free to read here on the web, and the Helm Academy course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Helm Academy course, upgrade to CoddyKit PRO.
What will I learn in “Hosting a Chart Repository”?
Serving charts over HTTP or object storage. You practise Helm Academy with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.
Do I need any experience to start Helm Academy?
No prior experience is required. Helm Academy on CoddyKit is structured for beginners through advanced learners; this is — lesson 3 of 4, so you can start here or from the beginning and move at your own pace.
How long does the “Hosting a Chart Repository” lesson take?
Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.
Can I write and run code in this Helm Academy lesson?
Yes. Every Helm Academy lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.