helm/chartmuseum
Chartmuseum
ChartMuseum is a centralized server for hosting, versioning, and distributing Kubernetes package repositories. It functions as a Kubernetes package manager and an OCI compatible registry, providing a system to manage the full lifecycle of software artifacts from upload and versioning to verification and deletion.
The project supports multitenant repository hosting by organizing packages into isolated namespaces for different teams and organizations. It utilizes a storage abstraction layer that allows packages to be persisted to local filesystems or S3 compatible cloud object stores, including Google Cloud Storage and Azure Blob Storage.
Additional capabilities include securing distribution via a private registry with TLS encryption and API access authentication using bearer tokens, basic auth, or client certificates. The server manages repository discovery through dynamic index generation and provides performance metrics export for system monitoring.
Features
- Helm Chart Management - Serves as a centralized host for packaged Kubernetes charts and provenance files for installation and verification.
- OCI Compatible Registries - Provides a full OCI-compliant registry server for distributing Kubernetes deployment packages.
- Namespace-Based Isolation - Organizes packages into isolated hierarchical directory structures to separate different organizations or projects.
- Chart Registries - Functions as a centralized server for hosting, versioning, and distributing Kubernetes package repositories.
- Helm Package Storage - Stores and serves package files and provenance files to enable the server to function as a repository.
- Package Lifecycle Management - Manages the full lifecycle of Kubernetes software artifacts from upload and versioning to verification and deletion.
- Multitenant Package Repositories - Provides a repository server that organizes packages into isolated namespaces for different teams and organizations.
- Multitenant Repository Hosting - Provides isolated namespaces and separate repositories for multiple teams or organizations on a single server.
- Chart Versioning APIs - Provides API endpoints for uploading new releases, deleting old versions, and retrieving chart metadata.
- API Client Authentications - Secures repository access using bearer tokens, basic authentication, and client certificates.
- Request Authentication Middleware - Intercepts incoming requests to validate identities via basic auth, bearer tokens, or TLS certificates.
- TLS Traffic Encryption - Ensures secure data transmission by serving all content over HTTPS with TLS encryption.
- Tenant-Based Directory Organization - Organizes packages into a hierarchical directory structure to isolate different organizations or projects.
- Cloud Object Storage - Persists packaged software and provenance files to remote cloud object stores including S3 and Azure Blob Storage.
- External Cache Integrations - Supports offloading in-memory chart indexes to external cache stores to reduce memory usage.
- Local Filesystem Storage - Saves Kubernetes charts and provenance files directly to the local server filesystem.
- Private Package Registries - Secures Kubernetes package distribution using authentication and TLS encryption to restrict access to internal software.
- Dynamic Index Generators - Automatically computes and serves a repository index file to enable client-side package discovery.
- CI Artifact Managers - Stores packaged application versions in cloud or local storage for integration with automated deployment pipelines.
- S3-Compatible Storage Adapters - Implements storage adapters to allow persistence of artifacts in S3-compatible object stores.
- Storage Abstraction Layers - Decouples the API from physical storage by routing operations to local filesystems or cloud object stores.
