import-from-flux

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

2|2|Updated Apr 15, 2026

Search Tags:#gitops #import #flux #helmrelease #confighub #kustomization #dry-wet-units

Ready to run

npx skills add https://github.com/confighub/confighub-skills --skill import-from-flux

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: import-from-flux
Source: https://github.com/confighub/confighub-skills/tree/main/skills/import-from-flux
Command: npx skills add https://github.com/confighub/confighub-skills --skill import-from-flux

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Flux resources like HelmReleases and Kustomizations can be managed via ConfigHub to add governance, validation, and policy before deployment, while Flux continues to deploy from its sources.

Core Features & Use Cases

Onboard Flux pipelines into ConfigHub without removing Flux from the cluster.
Rendered manifests from Flux are stored as wet Units for review, validation, and policy gates.
Use Case: A team with 20 HelmReleases wants ConfigHub to validate and gate changes before Flux applies them.

Quick Start

Describe how to import Flux-managed HelmRelease and Kustomization resources into ConfigHub so that ConfigHub validates, gates, and previews changes while Flux continues to deploy.

Frequently Asked Questions about import-from-flux

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

FAQPage Schema

How do I add policy validation to Flux HelmRelease resources without removing Flux from my cluster?▼

Importing Flux HelmRelease and Kustomization resources creates dry and wet Unit pairs in ConfigHub using cub gitops discover and cub gitops import commands. It sets ProviderType to FluxOCI and suspends the original Flux resources until validation is complete.

Can I use ConfigHub to gate HelmRelease changes while Flux continues to deploy from its sources?▼

ConfigHub integrates with Flux to place validation, policy, and approvals between GitOps rendering and in-cluster deployment. Rendered manifests from Flux are stored as wet Units for review, validation, and policy gates before deployment proceeds.

What is the process to onboard existing Kustomization resources into ConfigHub for governance?▼

ConfigHub onboards Flux pipelines by creating dry and wet Unit pairs from HelmRelease and Kustomization resources. It applies governance, validation, and policy gates before deployment while Flux continues to deploy from its sources.

Does importing Flux resources into ConfigHub require suspending the original HelmRelease and Kustomization manifests?▼

Yes, importing Flux resources suspends the original HelmRelease and Kustomization manifests. The process renders dry and wet Unit pairs in ConfigHub and keeps the originals suspended until validation is complete.

What are the limitations of using ConfigHub governance with Flux for GitOps deployments?▼

Using ConfigHub governance with Flux requires suspending original HelmRelease and Kustomization resources during import and validation. Flux cannot apply changes to those specific resources until validation and policy gates are cleared.