What is cortex-helm-chart?

This repository provides a Helm chart for Cortex, a system for storing and querying Prometheus metrics at scale. The chart lets teams deploy Cortex into a Kubernetes cluster with a single command, rather than manually configuring each component. Cortex itself is a horizontally scalable, long-term storage backend for Prometheus monitoring data. Prometheus is great at collecting metrics, but it's typically single-node with limited storage. Cortex extends that by providing a distributed system that can ingest metrics from multiple Prometheus instances, store them durably in backends like Cassandra or cloud object storage, and expose a unified query API. This chart packages all the Cortex components, distributors, ingesters, queriers, compactors, alertmanager, and others, along with their default configurations. The chart requires two external dependencies. First, a key-value store like etcd or Consul for coordination between Cortex components. Second, a storage backend for the actual metrics data. The chart also bundles several Memcached instances for caching query results and chunks, which speeds up repeated queries. Teams can override dozens of configurable values, replica counts, resource limits, storage settings, probe timeouts, through a custom values file. This would be used by platform or DevOps teams running monitoring infrastructure on Kubernetes. A concrete example: a company with 50 Prometheus instances across multiple clusters could point all of them at a single Cortex deployment to centralize metrics storage, enable long-term retention beyond what individual Prometheus servers can hold, and query all metrics through one endpoint. The chart assumes you already understand Kubernetes concepts like pods, services, and persistent volumes, and it requires sufficient cluster resources since Cortex runs many separate components. One thing to note: the chart exposes extensive configurability through its values file, covering everything from individual component resource requests to storage backend credentials and caching behavior. This flexibility means teams can tailor deployments to their scale and infrastructure, but it also means there's a meaningful learning curve to understanding what each component does and how the pieces fit together.