Kube-Prometheus-Stack vs. Prometheus Stack: Are They the Same Thing?

Type this project's name into a search bar and you'll immediately notice a problem: nobody spells it the same way twice. Some write kube-prometheus-stack. Others write kube prometheus stack without hyphens, or shorten it to kube-prom-stack. Blog posts casually call it the prometheus stack or the prometheus grafana stack. And more than a few engineers confuse it with kube-prometheus — a real but entirely different project. This guide clears up the naming confusion once and for all.

Quick Answer

In almost every case, kube-prometheus-stack, kube prometheus stack, kube-prom-stack, prometheus stack helm chart, and kube stack prometheus all refer to the exact same open-source Helm chart: prometheus-community/kube-prometheus-stack. It bundles Prometheus, Grafana, Alertmanager, the Prometheus Operator, Node Exporter, and kube-state-metrics into one installable package for Kubernetes.

The one real exception is kube-prometheus without the "-stack" suffix — an older sibling project distributed as raw manifests rather than a Helm chart. We break down that distinction in detail below.

Why Does the Same Tool Have So Many Names?

The naming confusion isn't accidental — it comes from the project's own history. The Helm chart was originally published under the name prometheus-operator chart. As the chart grew to include far more than just the operator itself, the prometheus-community maintainers renamed it to kube-prometheus-stack to better reflect what it actually installs. Older blog posts, forum threads, and even some internal company wikis still reference the old name or a half-remembered variant of the new one.

On top of that, the way the chart is referenced in a terminal adds another layer of naming. When you run helm repo add prometheus-community and later helm install monitoring prometheus-community/kube-prometheus-stack, the repository name and the chart name appear together. Many people remember only fragments of that command, which is exactly why searches like prometheus community kube prometheus stack or helm kube-prometheus-stack are so common.

Finally, spoken and written language naturally drifts. Engineers talking in Slack rarely type out a full hyphenated chart name — "just spin up the prometheus stack" is faster to say than "install kube-prometheus-stack via Helm." Over time, that casual shorthand ends up in commit messages, READMEs, and eventually search queries.

Search engines and AI answer engines make this even less noticeable day-to-day, because they largely treat hyphenated and spaced-out phrases as equivalent. A query for kube prometheus stack returns essentially the same results as kube-prometheus-stack. That's convenient for the person searching, but it also means the informal names spread further — nobody gets corrected, so the shorthand keeps circulating.

Terminology Glossary: Every Variant Explained

Here is a reference table mapping the most common ways people write or search for this project to what each term actually means.

kube-prometheus vs. kube-prometheus-stack: The Distinction That Actually Matters

Of everything on this page, this is the one mix-up worth remembering. kube-prometheus and kube-prometheus-stack are related but genuinely different projects, maintained differently and installed differently.

kube-prometheus is the original project maintained by the prometheus-operator team on GitHub. It ships as a set of raw Kubernetes manifests generated with Jsonnet, giving teams complete, line-by-line visibility and control over every resource that gets deployed. It has no values.yaml file and is not installed with a single helm install command — it's applied directly with kubectl, or compiled from Jsonnet source.

kube-prometheus-stack is the Helm chart maintained by the prometheus-community organization. It packages the same core components — Prometheus Operator, Prometheus, Alertmanager, and Grafana — into a single Helm chart configurable through a values.yaml file. It trades a small amount of the raw manifests' transparency for dramatically faster setup and easier day-two maintenance through Helm upgrades.

In short: if you ran a single helm install command to get monitoring running, you are using kube-prometheus-stack. If your cluster's monitoring was deployed from a folder of YAML manifests or compiled Jsonnet, you are likely using kube-prometheus. Most teams starting fresh today choose the Helm chart for its simplicity — see our complete introduction to kube-prometheus-stack for the full picture.

This also clears up a specific search mix-up: if you looked for kube-prometheus helm chart, kube-prometheus helm, or kube prometheus helm chart hoping to find a Helm-installable version of the manifests project, that chart doesn't exist under that name — kube-prometheus was never packaged as a Helm chart. What you actually want is kube-prometheus-stack.

What's Actually Inside the Chart

Regardless of which name led you here, the chart itself installs the same well-known set of components:

1. Prometheus — the metrics collection and time-series storage engine at the core of the stack.
2. Prometheus Operator — manages Prometheus, Alertmanager, and scrape configuration through Kubernetes CRDs like ServiceMonitor and PrometheusRule.
3. Grafana — the visualization layer, shipped with 30+ pre-built dashboards.
4. Alertmanager — routes firing alerts to Slack, PagerDuty, email, and other channels; see our Alertmanager configuration guide.
5. Node Exporter — a DaemonSet exposing hardware and OS-level metrics from every node.
6. kube-state-metrics — exposes the state of Kubernetes objects such as deployments, pods, and jobs.

For teams that outgrow default local retention, the chart also integrates cleanly with Thanos for long-term, multi-cluster metric storage.

It's worth noting that none of these six components are exclusive to kube-prometheus-stack. Prometheus, Grafana, and Alertmanager are all independent open-source projects you could install and wire together by hand. What the chart actually provides is the glue: the Prometheus Operator's CRDs, sane default alert rules, pre-loaded Grafana dashboards, and a single values.yaml surface for tuning all of it together. That packaging — not the individual tools — is what people are really referring to when they say "prometheus stack" or "prometheus grafana stack."

Installing It, Whatever You Call It

No matter which name brought you here, the installation command is the same three steps:

# 1. Add the prometheus-community Helm repository
helm repo add prometheus-community https://prometheus-community.github.io/helm-charts
helm repo update

# 2. Create a dedicated monitoring namespace
kubectl create namespace monitoring

# 3. Install the chart — this is the "kube-prometheus-stack" everyone means
helm install monitoring prometheus-community/kube-prometheus-stack \
  --namespace monitoring \
  --create-namespace

The repository name (prometheus-community) and chart name (kube-prometheus-stack) are separate pieces — which is exactly why the combined phrase prometheus community kube prometheus stack shows up so often in searches. Now you know both halves.

Does It Matter Which Name You Use Day to Day?

For casual conversation, no — everyone on a platform team already understands what you mean, whether you say "prometheus stack" or "kube-prom-stack." But precision starts to matter the moment you move from talking to doing. Three situations where it pays to use the exact name:

Filing a GitHub issue or asking for help. The maintainers track issues under the exact repository prometheus-community/helm-charts. Vague or incorrect naming in a bug report slows down triage.

Writing internal documentation. A runbook that says "the prometheus stack" without specifying the Helm chart and version leaves the next engineer guessing whether you mean this chart, the standalone kube-prometheus manifests, or a completely custom install.

Pinning dependencies. Helm, Terraform, and ArgoCD all reference the chart by its exact name and repository URL. There's no room for shorthand in a Chart.yaml or an ArgoCD Application manifest.

Frequently Asked Questions

Is kube-prom-stack the same as kube-prometheus-stack?

Yes. It's an informal shorthand used in chat, blog posts, and casual conversation — there is no separate project by that exact name.

What does prometheus-community/kube-prometheus-stack mean?

It's the fully qualified Helm reference: prometheus-community is the Helm repository, and kube-prometheus-stack is the chart name within it.

Is kube-prometheus-stack the same as kube-prometheus?

No — kube-prometheus is the older, manifest-based project; kube-prometheus-stack is the Helm chart. See the distinction above for details.

Which name should I use when asking for help or filing an issue?

Use the exact chart name, kube-prometheus-stack, and reference the prometheus-community/helm-charts repository — precise naming gets you to the right GitHub issues, Slack threads, and Stack Overflow answers faster.

Conclusion

Whether you searched for kube-prometheus-stack, kube-prom-stack, prometheus stack helm chart, or kube stack prometheus, you were almost certainly looking for the same thing: the prometheus-community/kube-prometheus-stack Helm chart. The only name that actually points somewhere different is kube-prometheus without the "-stack" suffix.

Now that the terminology is settled, the rest of this site walks through everything else you need: what the chart does, how to configure it, and how to run it in production.