Create a Helm Artifact

Convert your existing Helm charts into Bluebricks packages to deploy them across multiple environments with consistent configuration and automated management.

Prerequisites

• Bluebricks CLI installed

• Authenticated with Bluebricks (bricks login)

• Existing Helm chart with Chart.yaml and values.yaml

• Access to a Kubernetes cluster (EKS, GKE, or AKS)

• kubectl configured with cluster access

Quick Start

1. Prepare your Helm chart directory:

cd ~/my-helm-chart

1. Run blueprint prepare:

# Option 1: In-place (keeps original files)
bricks blueprint prepare --source . --iac-type helm

# Option 2: With output directory (copies files to src/helm/)
bricks blueprint prepare --source . --output ./dist --iac-type helm

1. Verify the generated package:

ls -la
# In-place: Shows bricks.json + original files
# With output: Shows bricks.json + src/helm/ directory

1. Publish the package:

bricks blueprint publish

That's it! Your Helm chart is now a Bluebricks package ready for deployment.

How It Works

When you run bricks blueprint prepare, Bluebricks:

• Validates your Chart.yaml and values.yaml to understand your chart structure

• Copies your files to src/helm/ when using the --output flag

• Generates a basic bricks.json manifest with type: "helm"

• Prepares the package for publishing (actual value extraction happens during bricks blueprint publish)

This transformation lets you manage Helm charts alongside other infrastructure types with consistent tooling.

Example Structure

Before:

my-helm-chart/
├── Chart.yaml
├── values.yaml
└── templates/
    ├── deployment.yaml
    └── service.yaml

After (with output directory):

my-helm-chart/
├── bricks.json          # Generated metadata
└── src/
    └── helm/            # Your files (copied)
        ├── Chart.yaml
        ├── values.yaml
        └── templates/

After (in-place, no output directory):

my-helm-chart/
├── bricks.json          # Generated metadata
├── Chart.yaml           # Original files remain
├── values.yaml
└── templates/

Test Your Package

Verify your Helm package works correctly before publishing:

# Dry run (plan only)
bricks run . --dry

# With custom properties
bricks run . --dry --props-file properties.json

The dry run shows you exactly what Helm will deploy without making any changes to your cluster.

See also

• Helm CRD Management -- automatic CRD handling with FluxCD SSA

• Packages overview -- artifact types and packaging concepts

• How to Create Blueprints -- compose artifacts into blueprints