skills.rest
confighub
confighubOFFICIAL
Explore all skills by this author →
WebsiteGitHub

import-from-helm

Render Helm charts into ConfigHub Units and manage upgrades with cub.

2|2|Updated Apr 15, 2026
Search Tags:#kubernetes#helm#gitops#crds#clone-workflow#confighub#unit-rendering
One-click install
npx skills add https://github.com/confighub/confighub-skills --skill import-from-helm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: import-from-helm
Source: https://github.com/confighub/confighub-skills/tree/main/skills/import-from-helm
Command: npx skills add https://github.com/confighub/confighub-skills --skill import-from-helm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helm charts are not natively managed as ConfigHub Units, so this skill enables onboarding and ongoing management of Helm charts inside ConfigHub.

Core Features & Use Cases

  • Renders charts into ConfigHub Units via cub helm install, then manages upgrades via cub helm upgrade, with clone-based customization preserving user edits.
  • Splits CRDs into their own Unit and hands off applying to cub-apply for controlled rollout in GitOps environments.
  • Avoids load for ArgoCD/Flux discovery and provides paths for import-from-argocd / import-from-flux or import-from-cluster flows.

Quick Start

Install the Helm chart into a ConfigHub Space by running cub helm install, then clone and mutate as needed.

Frequently Asked Questions about import-from-helm

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

FAQPage Schema
How do I migrate Helm charts into ConfigHub?▼

Migrate Helm charts into ConfigHub by rendering them as Units using cub helm install, then manage ongoing upgrades via cub helm upgrade while preserving user edits across clone-based customizations.

Can I preserve my custom Helm configurations across upgrades in ConfigHub?▼

Yes, configurations are preserved across upgrades by cloning rendered Helm Units and customizing them per environment, ensuring user edits are retained when running cub helm upgrade.

How does importing Helm charts handle CRDs in a GitOps workflow?▼

Importing Helm charts splits Custom Resource Definitions into their own dedicated Unit, handing off the application process to cub-apply to ensure controlled rollout within GitOps environments.

Does importing Helm charts to ConfigHub work with ArgoCD or Flux?▼

Yes, importing Helm charts avoids cluster load for non-ConfigHub discovery flows and provides dedicated integration paths for import-from-argocd, import-from-flux, and import-from-cluster workflows.

What do I need to manage Helm charts inside ConfigHub?▼

You need a Helm chart, access to the cub command-line tool, and a target ConfigHub Space, with optional prerequisites including kubectl and a reachable ConfigHub server for full functionality.

Why should I render Helm charts as Units instead of managing them natively?▼

Rendering Helm charts as Units enables native ConfigHub management, allowing clone-based per-environment customization and safe upgrades while avoiding cluster load for non-ConfigHub discovery flows.

Related Skills

Explore More Software Engineering Skills→
confighubconfighub
2

skill-examples-bootstrap

Bootstrap a ConfigHub playground Space with seed Kubernetes Units.

Official
Intermediate
confighubconfighub
2

import-from-flux

Import Flux HelmRelease and Kustomization resources into ConfigHub as dry and wet Units.

Official
Intermediate
confighubconfighub
2

import-from-argocd

Import ArgoCD Applications into ConfigHub as dry and wet Units.

Official
Advanced
confighubconfighub
2

import-from-cluster

Import live Kubernetes cluster state as literal YAML into ConfigHub Units.

Official
Advanced