Skip to main content

Helm chart

Install a chart from a public Helm or OCI repository. You pick the chart and its version and override the values you need; AstroPulse installs it as a Helm release on your cluster and keeps the cluster matching what you set. No chart yet? Ask Nova to write one for your service: it produces a complete chart you can push to a repository.

Before you start​

  • A cluster with an application profile. The wizard picks or creates one for you.
  • A chart in a public repository the cluster can reach: an HTTPS chart repository, or an OCI registry (oci://).
  • For a chart in a private repository, use Git repository instead: it reads the chart from a GitHub repository connected through the GitHub integration. The Helm chart source takes no repository credentials.

In the console​

  1. Open Workloads > Applications > Deploy application. Enter the Application name and pick the Target Cluster.

  2. On Profile, keep the profile picked for the cluster, or select Create New.

  3. On Chart, select Helm chart and enter the Helm Repository URL, for example https://stefanprodan.github.io/podinfo, or pick one with Browse Popular Repositories or Browse OCI Repositories.

  4. Pick the Chart Name from Matching charts, then the Chart Version. Pin a version, so every deploy installs the same chart. For an OCI registry the console cannot list charts: type the chart name and version. Optional: set the Helm Chart Release Name under Advanced Configuration; it cannot change after the first deploy.

    Open zoom view

    The Chart step with Helm chart: the podinfo repository, chart podinfo, version 6.17.0

    The Chart step with Helm chart: the podinfo repository, chart podinfo, version 6.17.0The Chart step with Helm chart: the podinfo repository, chart podinfo, version 6.17.0

  5. Optional: on Values, under Customize Helm Chart Values, change only the values you need and select Apply Overrides. "The chart renders with your values." means the chart templates cleanly with them.

  6. Select Review, run the dry run, then Deploy.

You should see​

The application's page in Workloads > Applications shows Running once the chart's resources are up, with its running configuration, events and logs.

Open zoom view

An application's Overview with its running configuration

An application's Overview with its running configurationAn application's Overview with its running configuration

If it does not start, its Events and Logs tabs say why: Troubleshoot.

Values​

Your overrides are merged over the chart's own values.yaml, so set only what differs. Read the chart's values.yaml for the keys it takes; the console shows it next to your overrides.

Update the chart or its values​

Open the application's Update tab, select Change configuration, and change the Chart Version or the values. Each deploy is a version you can roll back to. How the pods are replaced is the chart's own rollout setting, not AstroPulse's.

Reaching the application​

A Helm application is reached the way its chart exposes it: the chart's own Ingress or Service, set in its values. The Access step and Custom domain apply to image and model applications.

Other ways in​

With astroctl​

application.yaml
apiVersion: platform.astropulse.io/v1
kind: Application
spec:
  name: podinfo
  profileName: default-profile
  source:
    type: Helm
    helm:
      repo:
        repoURL: https://stefanprodan.github.io/podinfo
        chartName: podinfo
        chartVersion: 6.17.0
      values:
        object:
          replicaCount: 2
Terminal
astroctl app apply -f application.yaml --dry-run
astroctl app apply -f application.yaml

See the astroctl reference.

Settings​

The settings every source shares (name, profile, namespace, sync) are on Sources. These are specific to a Helm chart:

Helm Repository URLsource.helm.repo.repoURLRequired

The chart repository.

Accepts
An HTTPS chart repository, a Git SSH URL, or an OCI registry (oci://).
Chart Namesource.helm.repo.chartNameRequired

The chart to install from the repository.

Chart Versionsource.helm.repo.chartVersionRequired

The chart version. Pin one, so every deploy installs the same chart.

Helm Chart Release Namesource.helm.repo.releaseName

The Helm release name. Fixed once the application exists.

Default
The application's name.
Customize Helm Chart Valuessource.helm.values

Your overrides over the chart's values.yaml: object holds them inline. Set one of object or files.

If it's refused​

"Repository URL must be a valid HTTPS, Git SSH, or OCI URL"
Cause
The Helm Repository URL is not one of the three forms the source reads.
Fix
Use the repository's HTTPS URL, for example https://stefanprodan.github.io/podinfo, or oci:// for a registry.
"No charts found or repository not accessible"
Cause
The URL is not a chart repository, or it is private.
Fix
Check the URL serves an index.yaml. For a private chart, use Git repository.
"Chart listing is not supported for OCI repositories. Please enter the chart name and version manually."
Cause
An OCI registry does not publish a chart list.
Fix
Type the Chart Name and Chart Version.

Next​