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

# Install Hub

> Install the Metoro hub from pinned Helm chart values, Secrets, ingress, and first-login checks

> [!NOTE]
>
> The install steps, Secrets, values, and checks below use the decisions saved in Installation Planning.

> [card] Selected plan
>
> These choices are saved in this browser.
>
> Change them on the
> [Installation Planning page](https://metoro.io/docs/on-premises/12.x/installation/planning.md)
> .
>
> <ul />

**1. Confirm prerequisites**

<ul />

**2. Create the namespace**

Use `metoro-hub` as the hub namespace. This keeps Secrets,
ConfigMaps, and operational runbooks consistent across installations.

<pre>`kubectl create namespace metoro-hub`</pre>

**3. Prepare network, auth, and dependencies**

**4. Create required Secrets**

The chart references existing Kubernetes Secrets for credentials. Do not put secret values into the Helm values file.

**5. Prepare storage**

**6. Create the values file**

Save the values content as `metoro-hub-values.yaml`.

Fill in the `CHANGE_ME` values and keep credentials in
Kubernetes Secrets.

<pre />

**7. Log into quay**

Log into quay to be able to access the oci helm chart. You should use the credentials provided by your Metoro rep.

<pre>`helm registry login quay.io`</pre>

**8. Install with Helm**

Install from the published chart and pin an explicit chart version. The
Helm release name must be `metoro`; the chart fails fast for any other
release name.

<pre>`helm upgrade --install metoro oci://quay.io/metoro/charts/metoro-onprem \\   --namespace metoro-hub \\   --version 12.0.2 \\   --values metoro-hub-values.yaml`</pre>

**9. Wait for startup**

<ul />

**10. Run post-install checks**

### If telemetry pages error right after install

On a fresh cluster the apiserver comes up while the ingester is
still creating the telemetry tables, so telemetry pages (logs,
traces, metrics, Kubernetes views, profiles) can return errors for
the first few minutes while the rest of the UI works. This clears
on its own as soon as the ingester finishes creating the tables; no
restart is needed.

**11. Log in**

The chart creates `metoro-admin-bootstrap` with a generated
password and the organization name from
`bootstrap.organizationName`. Retrieve the generated password:

<pre>`kubectl -n metoro-hub get secret metoro-admin-bootstrap \\
  -o jsonpath='\{.data.password\}' | base64 -d; echo`</pre>

After the hub is ready, head to alerts and hit sync alerts to get predefined alerts running. Do the same for dashboards. Now you can connect monitored clusters from the Metoro UI.


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