> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ankra.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Chart sources

> Learn where the Helm charts in your Stacks come from - Ankra's catalogue, HTTP chart repositories and OCI registries - and which to use when.

Every Helm add-on in a [Stack](https://docs.ankra.ai/concepts/stacks.md) names a chart, a version and the registry the chart comes from. Ankra reads every registry your organisation can install from, indexes its charts, and offers them in one list: **Find a chart** in the stack editor, **Infrastructure → Managed services → Helm** in the portal, and `ankra helm addon-catalog` in the CLI. Behind that one list are three kinds of source.

## The three sources

| Source | What it is | Where it is added | Login |
| - | - | - | - |
| **Ankra's catalogue** | Preloaded registries Ankra provides to every organisation, with add-on definitions that group and describe their charts | Nowhere: every organisation has it | None |
| **HTTP chart repository** | A Helm repository serving an `index.yaml` over `https://`, such as ChartMuseum, Nexus, Artifactory or Harbor before 2.8 | **Build & delivery → Helm registries → Add registry** | Optional registry credential |
| **OCI registry** | Charts stored as OCI artifacts at an `oci://` address, such as GHCR, Amazon ECR, Google Artifact Registry, Azure Container Registry, Docker Hub or Harbor 2.8 and later | **Build & delivery → Registries → Connect a registry** | Optional; Harbor and Google Artifact Registry connections also let Ankra make robot accounts |

Ankra's catalogue lives in the public [ankraio/ankra-global-resources](https://github.com/ankraio/ankra-global-resources) repository, and anyone can propose a registry or an add-on for it by pull request ([Publishing add-ons](https://docs.ankra.ai/platform/addon-publishing.md)). The registries you add belong to your organisation, or to one of its projects when pinned to it, and no other organisation sees them.

The two kinds you add live on two pages because Ankra does more with an OCI registry. Connecting one checks its login and lists its projects, and for Harbor and Google Artifact Registry it can make the robot accounts your clusters pull with. An HTTP repository is only read. Once connected, both kinds appear side by side under **Helm registries**, where Ankra reads them on a schedule and you sync or remove them.

## Which to use

* **A public chart that Ankra's catalogue already has** (cert-manager, Grafana and the like): use it as it is. There is nothing to add.
* **A public chart from a project's own Helm repository**: add that repository as an HTTP chart repository, with no credential.
* **A public chart published as an OCI artifact** (Envoy Gateway on Docker Hub, for example): connect the registry as an OCI registry, with no credential.
* **Your own charts**: push them to a registry you control, usually the OCI registry that already holds your images, and connect it with a read-only login. [Host your own Helm charts](https://docs.ankra.ai/guides/create-a-registry.md) walks through GHCR.
* **A registry that holds many charts you never install**: list the ones to skip in **Charts to leave out** when you add it (`--exclude-charts` on the CLI), so Ankra does not index them.

## How a Stack refers to a chart

When you add a chart to a Stack, the add-on stores the chart's name, its pinned version and the registry it came from. A Stack never holds the registry's login. When the cluster deploys, it is given the login: the agent signs in with it on the native engine, and on an Argo CD cluster the login is kept as a repository Secret in Argo CD's namespace, and Argo CD pulls the chart with it. In a GitOps repository the same add-on reads:

```yaml theme={null}
addons:
- name: fluent-bit
  chart_name: fluent-bit
  chart_version: 0.49.1
  registry_name: fluent
  registry_url: https://fluent.github.io/helm-charts
  namespace: logging
```

Because the reference names the registry, the registry has to stay connected for the Stack to deploy. Deleting a registry takes its charts out of the list, and Stacks that install a chart from it fail their next deploy until it is connected again. A Stack cloned into another organisation needs the same registries connected there. The clone warns about each registry credential missing there; a missing registry makes the Stack fail when it deploys ([Clone Stacks](https://docs.ankra.ai/guides/clone-stack.md)).

## Credentials

A private registry signs in with a registry credential: a username and a password or token. You store it once, under **Registry credentials** on **Helm registries**, under **Integrations & alerts → Credentials** as a **Helm registry**, or with `ankra helm credentials create`, and pick it when you add the registry. The portal says Ankra keeps the login encrypted and never shows it again. Give it the least access that works: a token that can read charts, not one that can push.

## Where to go next

* [Connect a Helm registry](https://docs.ankra.ai/guides/registries.md) - add an HTTP repository or an OCI registry, step by step.
* [Charts and the add-on catalogue](https://docs.ankra.ai/platform/addon-catalog.md) - browse charts, read their values and licence, curate add-ons.
* [Create and change a stack](https://docs.ankra.ai/guides/create-and-change-a-stack.md) - add a chart to a Stack and deploy it.
* [Helm registry CLI reference](https://docs.ankra.ai/reference/cli/helm.md) - every `ankra helm` command.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.