> ## Documentation Index
> Fetch the complete documentation index at: https://mogenius-docs-self-hosted-helm-values-update.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Helm charts

mogenius includes a Helm chart manager that simplifies managing Helm repositories and releases on your cluster. With this feature, you can monitor installed charts on your cluster and easily install new ones.

<Note>
  Helm charts are currently available on the **Clusters** page. We’re working on enabling Helm charts within projects.
</Note>

## Accessing the Helm Charts UI

To use the Helm charts manager, go to the **Clusters** page within your organization. If you don’t have a Kubernetes cluster connected yet, refer to our [quickstart guide](../overview/quickstart.md). Once inside the cluster, navigate to the **Helm Charts** tab.

This page displays:

* All installed Helm repositories on the cluster.
* A list of Helm releases, including their status, versions, namespace, and age.

By opening a release, you can view:

* Detailed information about the Kubernetes resources managed by the Helm chart.
* Configuration files, such as `values.yaml`, which define the chart's setup.

## Adding a Helm Repository

To add a new Helm repository, use the **Add Repository** button at the top of the page. Fill out the following fields in the menu that appears:

* **Name**: Internal name to display the chart.
* **Repository URL**: The URL of the Helm repository you want to install.
* **User Name and Password Credentials (optional)**: Provide credentials if the repository requires authentication.
* **Skip TLS**: Enable this option to skip TLS during authentication (optional).

Once the repository is installed, its charts will be available for installation. When adding a repository, the latest versions of its charts are automatically retrieved. If charts in a repository are updated later, use the **Update All** button to fetch the latest versions.

## Installing from Blueprints

When installing a chart, you can also choose from the [Blueprints](/cluster-management/blueprints) library. Blueprints are pre-configured charts for common infrastructure services (ingress controllers, monitoring, TLS, etc.) with sensible defaults. Select a Blueprint instead of a repository chart, customize the values if needed, and deploy — the result is a standard Helm release managed here.

## Installing a Helm Chart

To install a new Helm chart, click the **Install Chart** button. Here's how to proceed:

1. **Select the Chart**: Choose the chart you want to install from the list or search for it by name.
2. **Configure the Release**: Fill out the following settings:
   * **Version**: Select the desired chart version from the list of available versions in the repository.
   * **Release Name**: Specify an internal name for the Helm release.
   * **Namespace**: Select the namespace where the chart will be installed. All resources from the chart will be deployed into this namespace.
     * We recommend creating a new namespace for your chart to prevent conflicts with other applications on the cluster. Use the **Create New Namespace** button to quickly create one.
   * **Chart Values Reference**: Review the default chart values. Most charts should install successfully with default values for testing purposes. You can refine the configuration later with custom values.
   * **User-Defined Values**: To modify default chart configurations or fill out template values, use the YAML editor. Copy sections from the chart values reference and overwrite them with your configurations. A custom `values.yaml` file will then be applied during chart installation.
3. **Confirm Settings**: Once your configurations are complete, confirm your settings to start the installation. You can monitor the installation process through the logs.

After installation, the release will appear in the list, and its status should change to `Deployed`. If errors occur, check the logs and adjust the release configuration as needed.

## Installing from OCI Registries

In addition to traditional Helm repositories, mogenius supports installing charts from OCI-compliant registries such as GitHub Container Registry (ghcr.io), Amazon ECR, Google Artifact Registry, or Docker Hub.

To install an OCI chart:

1. Click **Install OCI Chart** on the Helm Charts page.
2. Enter the **OCI Chart URL** in the format `oci://registry/repository/chart` (e.g., `oci://ghcr.io/myorg/my-chart`).
3. Optionally provide **registry credentials** if the chart requires authentication.
4. Select the **version**, **release name**, and **namespace** as with standard chart installations.
5. Configure custom values if needed and confirm to install.

<Tip>
  OCI registries are increasingly common for distributing Helm charts. If your organization uses GitHub Packages, ECR, or a similar registry for container images, you can likely store Helm charts there as well.
</Tip>

## Upgrading a Helm Release

To upgrade an existing release to a new chart version or apply updated values:

1. Open the release details by clicking on a release in the list.
2. Click **Upgrade** to open the upgrade dialog.
3. Select the new **chart version** from the available versions.
4. Review and modify the **values** as needed. The current values are pre-filled for reference.
5. Confirm to start the upgrade.

The upgrade process creates a new revision of the release. You can monitor progress in the logs. If the upgrade succeeds, the release status updates to `Deployed` with the new version.

<Note>
  Upgrading a release preserves its revision history, allowing you to roll back if needed.
</Note>

## Rolling Back a Release

If an upgrade introduces issues, you can roll back to a previous revision:

1. Open the release details by clicking on a release in the list.
2. Click **Rollback** to open the rollback dialog.
3. Select the **revision** you want to restore from the list of previous revisions. Each revision shows the chart version and description.
4. Confirm to roll back.

The rollback creates a new revision that restores the previous configuration. This is a safe operation — the previous revisions remain available in case you need to roll back again or roll forward.

<Tip>
  Before rolling back, review the revision details to understand what configuration was active at that point. This helps ensure you're restoring to the correct state.
</Tip>

## Linking Releases to Workspaces

Helm releases installed at the cluster level can be linked to a Workspace for easier monitoring and access control. When a release is linked to a Workspace:

* Workspace members can view the release status and resources
* The release appears in the Workspace's resource list
* Access is governed by Workspace roles

To link a release to a Workspace:

1. Open the release details.
2. Click **Link to Workspace**.
3. Select the target Workspace from the list.
4. Confirm to create the link.

This is useful when a platform team installs shared infrastructure (databases, message queues, etc.) that application teams need to monitor but not manage directly.

## Uninstalling a Release

To remove a Helm release from your cluster:

1. Open the release details by clicking on a release in the list.
2. Click **Uninstall** (or use the actions menu).
3. Confirm the uninstallation.

<Warning>
  Uninstalling a release deletes all Kubernetes resources managed by that release. This action cannot be undone. Make sure to back up any important data before uninstalling.
</Warning>

The uninstallation process removes the release and its resources from the cluster. Once complete, the release will no longer appear in the list.