Skip to content

ChartMuseum v0.5.0
Compare
Choose a tag to compare
@jdolitsky jdolitsky released this 03 Apr 21:00
v0.5.0
981ac2e

Warning: v0.5.0 introduces a regression for Microsoft Azure users, please upgrade to v0.5.1!

MULTITENANT SUPPORT!!!

Multitenancy is now supported with the --depth flag!

To begin, start with a directory structure such as

charts
├── org1
│   ├── repo1
│   │   └── nginx-ingress-0.9.3.tgz
├── org2
│   ├── repo1
│   │   └── chartmuseum-0.4.0.tgz

This represents a storage layout appropriate for --depth=2. The organization level can be eliminated by using --depth=1. The default depth is 0 (singletenant server).

Start the server with --depth=2, pointing to the charts/ directory:

chartmuseum --debug --depth=2 --storage="local" --storage-local-rootdir=./charts

This example will provide two separate Helm Chart Repositories at the following locations:

  • helm repo add org1-repo1 http://localhost:8080/org1/repo1
  • helm repo add org2-repo1 http://localhost:8080/org2/repo1

This should work with all supported storage backends.

To use the chart manipulation routes, simply place the name of the repo directly after "/api" in the route:

curl -F "chart=@mychart-0.1.0.tgz" http://localhost:8080/api/org1/repo1/charts

Also in this release:

  • Migrated from glide to dep (#81)
  • General code cleanup, refactoring

Big thanks to everyone involved in making this happen!

Assets 2
Loading