Skip to main content
Helm releases represent deployed instances of Helm charts in your cluster. You can view release status, chart information, deployed resources, revision history, and related events.

​
Key Concepts

Helm Release

A deployed instance of a Helm chart with a specific configuration.

Chart

A Helm package containing Kubernetes resource templates and default values.

Revision

A version of the release. Each upgrade or rollback creates a new revision.

Values

Configuration values used to customize the chart deployment.

​
Required Permissions

ActionPermission
View releasesiam:project:infrastructure:kubernetes:read
Delete releaseiam:project:infrastructure:kubernetes:delete
Helm releases are managed externally via Helm CLI or CD tools. The platform provides read-only visibility and the ability to delete releases.

​
Release Status Values

StatusDescription
deployedRelease is successfully deployed and running
failedRelease deployment or upgrade failed
pending-installInitial installation in progress
pending-upgradeUpgrade operation in progress
pending-rollbackRollback operation in progress
supersededPrevious revision, replaced by a newer one
uninstallingUninstall operation in progress

​
How to View Helm Releases

1

Select Cluster

Choose a cluster from the cluster dropdown.
2

Select Namespace

Choose a namespace to filter releases, or select “all” to view releases across all namespaces.
3

Filter and Search

Use the search box to find releases by name, chart, or namespace. Filter by status (Deployed, Failed, Pending, Superseded).

​
How to View Release Details

1

Find the Release

Locate the release in the list.
2

Click Release Name

Click on the release name to open the detail drawer.
3

Review Details

View comprehensive release information including:
  • Overview: Name, namespace, revision, age, deployment timestamps
  • Chart Info: Chart name, chart version, app version, description
  • Resources: Deployments, StatefulSets, DaemonSets, Services, and Pods created by the release
  • Revision History: All revisions with status, chart version, and timestamps
  • Events: Kubernetes events related to the release resources

​
How to Delete a Helm Release

1

Find the Release

Locate the release in the list.
2

Open Actions Menu

Click the actions menu (three dots) on the release row.
3

Click Delete Release

Select Delete Release from the menu.
4

Confirm

Review the warning and confirm the deletion.
Deleting a Helm release only removes the release metadata (Helm secrets). The actual resources deployed by the chart (Deployments, Services, ConfigMaps, etc.) will remain in the cluster unless they were created with owner references to the release. Delete resources separately if needed.

​
Understanding Release Resources

When viewing a release’s details, the Resources section shows Kubernetes objects created by the chart:
Resource TypeWhat It Shows
DeploymentsName, replica count, ready replicas
StatefulSetsName, replica count, ready replicas
DaemonSetsName, desired nodes, ready nodes
ServicesName, type, cluster IP, ports
PodsName, phase, ready status
Resources are identified by common Helm labels: app.kubernetes.io/instance, release, or app matching the release name.

​
Understanding Revision History

Each Helm operation creates a new revision:
  • Install: Creates revision 1
  • Upgrade: Creates a new revision (2, 3, 4…)
  • Rollback: Creates a new revision with the old configuration
The history shows:
  • Revision number
  • Status at that revision
  • Chart version used
  • Timestamp
  • Description (upgrade notes)
Helm keeps release history as Kubernetes secrets with the owner=helm label. By default, Helm retains the last 10 revisions.

​
Troubleshooting

  • Check the Events section for error details
  • Review pod logs for application errors
  • Verify ConfigMaps and Secrets exist
  • Check resource quota limits in the namespace
  • Use helm history <release> CLI command for more details
  • Check if pods are starting successfully
  • Review events for scheduling issues
  • Verify node resources are available
  • Check for PVC binding issues if using persistent storage
  • Ensure resources have standard Helm labels
  • Check app.kubernetes.io/instance=<release-name> label
  • Some charts use custom labeling schemes
  • Verify the correct namespace is selected
  • Check if the release was installed in a different namespace
  • Helm secrets may have been manually deleted
  • Platform deletion only removes Helm metadata
  • Use kubectl delete to remove remaining resources
  • Or reinstall and use helm uninstall for clean removal
  • Helm secrets may have been deleted
  • Check helm.sh/release-max-history setting
  • Old revisions are automatically pruned based on history limit

​
FAQ

Currently, the platform provides read-only access to Helm releases. Use the Helm CLI or your CD pipeline to perform upgrades and rollbacks.
Helm stores release information as Kubernetes secrets with the owner=helm label. Each revision is stored as a separate secret containing the release manifest, values, and chart metadata.
Platform deletion removes only the Helm secrets (metadata). helm uninstall removes both the metadata AND all resources deployed by the chart. Use helm uninstall for a complete cleanup.
Each upgrade creates a new revision and marks the previous one as superseded. This is normal and allows rollbacks to previous configurations.
By default, Helm keeps the last 10 revisions. This can be configured with --history-max flag during install/upgrade or the HELM_MAX_HISTORY environment variable.
The current view shows chart and version information. For detailed values, use helm get values <release> CLI command.
Resources need Helm-standard labels to be associated with a release. If a chart uses custom labels or creates resources without proper labeling, they won’t appear in the resources list.
The workloads continue running. Deleting the release only removes Helm’s tracking metadata. The Deployments, Services, and Pods remain active until manually deleted.