Helm

Overview

Helm is the package manager for Kubernetes. It uses charts to define, install, and manage Kubernetes applications.

JFrog Fly supports Helm charts via OCI (Open Container Initiative) registry, the modern standard for distributing Helm charts.

Integrating Helm with JFrog Fly allows you to manage your charts and releases from source code to production in a simple and native way, right from your coding agent.

Upload / Push Chart

With Fly App

Activate Helm in your Fly App to automatically authenticate, then push your chart:

helm push my-chart-1.0.0.tgz <your-fly-subdomain>.jfrog.io/helmoci

Manual Configuration

1. Generate an access token in Fly Token Management

2. Login to the Helm OCI registry:

helm registry login <your-fly-subdomain>.jfrog.io -u <your-fly-username> -p <your-fly-token>

3. Package your chart (if not already packaged):

helm package my-chart/

4. Push your chart:

helm push my-chart-1.0.0.tgz <your-fly-subdomain>.jfrog.io/helmoci

Download / Pull Chart

With Fly App

Activate Helm in your Fly App to automatically authenticate, then pull your chart:

helm pull <your-fly-subdomain>.jfrog.io/helmoci/my-chart --version 1.0.0

Manual Configuration

1. Generate an access token in Fly Token Management

2. Login to the Helm OCI registry:

helm registry login <your-fly-subdomain>.jfrog.io -u <your-fly-username> -p <your-fly-token>

3. Pull your chart:

helm pull <your-fly-subdomain>.jfrog.io/helmoci/my-chart --version 1.0.0

Install Directly

You can install a chart directly from Fly Registry without pulling first:

helm install my-release <your-fly-subdomain>.jfrog.io/helmoci/my-chart --version 1.0.0

Push/Pull Charts with CI

To push and pull Helm charts with CI, update your GitHub Actions workflow to include the Fly action.

Simply ask your coding agent: “Configure my workflows with Fly” and Fly MCP will configure your GitHub Actions workflow yml file, as follows:

1. Add permissions (top level, after on:):

permissions:
  contents: read
  id-token: write

2. Add Fly Action (after setup steps, before artifact operations):

- name: JFrog Fly - Configure all your package managers to work with Fly registry
  uses: jfrog/fly-action@v1

3. Push your chart using your Fly registry path: <your-fly-subdomain>.jfrog.io/helmoci

GitHub Action Example

name: Package and Push Helm Chart

on:
  push:
    branches: [main]

permissions:
  contents: read
  id-token: write

jobs:
  helm:
    runs-on: ubuntu-latest

    steps:
      - name: Checkout code
        uses: actions/checkout@v4

      - name: JFrog Fly - Configure all your package managers to work with Fly registry
        uses: jfrog/fly-action@v1

      - name: Package Helm chart
        run: helm package my-chart/

      - name: Push Helm chart
        run: helm push my-chart-1.0.0.tgz <your-fly-subdomain>.jfrog.io/helmoci

Back to Package Types →