ChartMuseum v0.5.0

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 "[email protected]" 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!

ChartMuseum v0.4.2

• Upgrade to Helm v2.8.2 (#68)
• Give root route same access at index.yaml (#66)

ChartMuseum v0.4.1

• --index-limit=<number> flag added, which allows limiting the number of parallel indexers. This is a fix for #58. Thanks @sjthespian!
• --context-path=<path> flag added, which enables using a custom base context path (new root for application routes). Thanks @rpahli!

ChartMuseum v0.4.0

Support for Alibaba Cloud OSS Storage has been added (thanks @denverdino)!

Make sure your environment is properly setup to access my-oss-bucket.

To do so, you must set the following env vars:

• ALIBABA_CLOUD_ACCESS_KEY_ID
• ALIBABA_CLOUD_ACCESS_KEY_SECRET

chartmuseum --debug --port=8080 \
  --storage="alibaba" \
  --storage-alibaba-bucket="my-oss-bucket" \
  --storage-alibaba-prefix="" \
  --storage-alibaba-endpoint="oss-cn-beijing.aliyuncs.com"

ChartMuseum v0.3.1

• Add HTML welcome page to root route, "/" no longer returns 404 (#46)
• Fix issue with Azure backend reloading chart packages despite no changes (#47)

ChartMuseum v0.3.0

Support for Microsoft Azure Blob Storage has been added!

Make sure your environment is properly setup to access mycontainer.

To do so, you much set the following env vars:

• AZURE_STORAGE_ACCOUNT
• AZURE_STORAGE_ACCESS_KEY

chartmuseum --debug --port=8080 \
  --storage="azure" \
  --storage-microsoft-container="mycontainer" \
  --storage-microsoft-prefix=""

Also:

• Upgraded to Helm v2.8.1
• Added --storage-amazon-sse=<algorithm> option (#38)

Happy Valentine's Day 💘
- The ChartMuseum Developers

ChartMuseum v0.2.8

• Upgrade to Helm v2.8.0
• --auth-anonymous-get flag added, allowing anonymous read for GET operations when basic auth is enabled (#34)
• IAM Policy for S3 Storage in documentation (#31)
• Added code-of-conduct.md

ChartMuseum v0.2.7

• Added "http auth free" health endpoint at /health (#28)
• Documentation added about community/slack, helm chart PRs, and env vars (#26)

ChartMuseum v0.2.6

• Upgrade to Helm v2.7.2
• Detect chart versions with suffix, such as mychart-1.0.4-SNAPSHOT.tgz (fix for #22)
• Add X-Request-Id header (implementation of #21)
• More robust logging

ChartMuseum v0.2.5

• Optimized index regeneration on high latency links to cloud storage. The service of /index.yaml is now done in constant time, even while uploading new charts. (0e9d2e3)

For chartmuseum development:

• Re-seated go import paths to their new kubernetes-helm home (e5d5b65)
• Added loadtesting framework
• Allow cloud testing even when some backends are not available (99ac1b9).