kubespray-helm-airgap

Package Helm charts as tgz and store them in OCI registries for air-gapped deployments.

6|2|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/sigridjineth/kubespray-skills --skill kubespray-helm-airgap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kubespray-helm-airgap
Source: https://github.com/sigridjineth/kubespray-skills/tree/main/kubespray-helm-airgap
Command: npx skills add https://github.com/sigridjineth/kubespray-skills --skill kubespray-helm-airgap

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill enables the deployment and management of Helm charts within air-gapped Kubernetes clusters, overcoming the challenge of accessing public repositories.

Core Features & Use Cases

  • Internal Chart Repositories: Set up and utilize ChartMuseum or OCI-compatible registries for storing Helm charts.
  • Offline Deployment: Package Helm charts and their container images, then deploy them without internet access.
  • Use Case: Deploying a complex application stack using Helm charts to a Kubernetes cluster in a secure, isolated network where external access is prohibited.

Quick Start

Use the kubespray-helm-airgap skill to push the packaged chart 'nginx-chart-1.0.0.tgz' to the internal OCI registry at '192.168.10.10:35000/helm-charts'.

Frequently Asked Questions about kubespray-helm-airgap

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy Helm charts in an air-gapped Kubernetes environment?

Helm air-gapped deployment works by packaging charts as tgz files, pushing them to an internal OCI registry or ChartMuseum, and deploying releases from these isolated sources without requiring internet access.

What Helm version is required for OCI registry support in isolated clusters?

Helm OCI registry support requires Helm 3.8 or higher to successfully push and pull packaged chart tgz files to and from your internal OCI-compatible registry.

Can I use ChartMuseum instead of an OCI registry for offline Helm deployments?

Yes, ChartMuseum can be set up as an internal chart repository for offline deployments, serving as an alternative to OCI registries to store and manage Helm charts.

What's the best way to package Helm charts for internal registries without internet access?

The best way to package Helm charts for internal registries is to bundle them as tgz files, which can then be pushed directly to an OCI registry or ChartMuseum for offline deployment.

How do I push a packaged Helm chart to an internal OCI registry?

To push a packaged Helm chart to an internal OCI registry, use Helm commands to push the tgz file to your registry endpoint, such as '192.168.10.10:35000/helm-charts'.

Why do I need to package container images alongside Helm charts for air-gapped deployments?

Packaging container images alongside Helm charts is necessary because air-gapped clusters cannot pull images from public repositories, ensuring applications run successfully without internet access.