Helm Chart

Perform operations on Helm charts

Actions2

Helm Chart Actions
- Get Default Values
- Get Chart Metadata

Overview

This node interacts with Helm chart repositories to retrieve metadata or default values of Helm charts. It is useful in scenarios where you want to programmatically access information about Helm charts stored in HTTP or OCI repositories, such as for automation pipelines that deploy or analyze Kubernetes applications.

Practical examples include:

Fetching the metadata of a specific Helm chart version to inspect its details before deployment.
Retrieving the default values.yaml content of a Helm chart to customize deployments dynamically.

Properties

Name	Meaning
Repository URL	URL of the Helm chart repository. For HTTP repositories, it should start with `http://` or `https://`. For OCI repositories, use `oci://` or leave the scheme empty.
Chart Name	The name of the Helm chart to query.
Chart Version	(Optional) Specific version of the Helm chart. If not provided, the latest version will be used.
Authentication	Boolean flag indicating whether authentication is required to access the Helm repository.
Credentials	The credentials used for authenticating with the Helm repository when authentication is enabled. These credentials typically include username and password or registry-specific tokens depending on the repository type.

Output

The node outputs an array with one item per input item. Each output item contains a json object with the following structure depending on the operation:

For Get Chart Metadata operation:
```
{
  "success": true,
  "metadata": { /* Helm chart metadata object */ }
}
```
The metadata field contains detailed information about the Helm chart, such as its description, version, maintainers, and other relevant metadata.
For Get Default Values operation (not requested but supported by the same properties):
```
{
  "success": true,
  "values": { /* Default values.yaml content as JSON */ }
}
```
The values field contains the default configuration values of the Helm chart.

If an error occurs and the node is configured to continue on failure, the output will contain:

{
  "success": false,
  "error": "Error message describing what went wrong"
}

The node does not output binary data.

Dependencies

Requires access to Helm chart repositories over HTTP(S) or OCI protocols.
If authentication is enabled, valid credentials must be provided.
Uses internal utility functions to determine repository type and fetch chart data.
No external API keys are explicitly required beyond the repository credentials.
No special environment variables are needed beyond standard n8n credential management.

Troubleshooting

Common issues:
- Missing or incorrect Repository URL: The node throws an error if the repository URL is not specified.
- Missing or incorrect Chart Name: The node throws an error if the chart name is not specified.
- Authentication failures: If authentication is enabled but credentials are invalid or missing, the node will fail to fetch data.
- Unsupported repository types or malformed URLs may cause errors.
Error messages:
- "Repository URL must be specified": Ensure the repository URL property is filled correctly.
- "Chart name must be specified": Provide a valid chart name.
- Authentication errors usually come from invalid credentials; verify username/password or registry tokens.
To handle errors gracefully, enable the "Continue On Fail" option so the workflow can proceed even if some items fail.