import-from-argocd

Import ArgoCD Applications into ConfigHub as dry and wet Units.

2|2|Updated Apr 15, 2026

Search Tags:#kubernetes #gitops #argocd #workflows #import #confighub #oci-registry

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Onboard ArgoCD-managed Deployments into ConfigHub to provide governance, validation, and policy while ArgoCD continues to operate.

Core Features & Use Cases

Discover existing ArgoCD Applications in the cluster and represent them as dry Units (the Application resource) and wet Units (rendered manifests) for ConfigHub governance.
Disable auto-sync on the in-cluster Application and manage approvals, validations, and mutations through ConfigHub before deployment.
Render manifests via the ArgoCDRenderer bridge and deploy through ConfigHub's OCI-based flow.

Quick Start

Run cub gitops discover to identify ArgoCD Applications, then run cub gitops import to create and link dry and wet Units in your import Space.

Frequently Asked Questions about import-from-argocd

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

FAQPage Schema

How do I import existing ArgoCD Applications into ConfigHub for governance?▼

To import ArgoCD Applications into ConfigHub, run cub gitops discover to identify them, then run cub gitops import to create and link dry and wet Units in your target Space for governance and policy enforcement.

Can I manage ArgoCD deployments with ConfigHub without removing ArgoCD from my cluster?▼

Yes, you can manage ArgoCD deployments with ConfigHub while preserving ArgoCD in the cluster. The import process disables auto-sync on the in-cluster Application, allowing ConfigHub to manage approvals and validations before deployment.

What prerequisites are needed to onboard ArgoCD apps into ConfigHub?▼

Prerequisites for onboarding ArgoCD apps include a Worker with ArgoCD bridges configured, a target Space, access to cub gitops commands, and ARGOCD_SERVER and ARGOCD_AUTH_TOKEN environment variables set to render manifests.

How does ConfigHub render Kubernetes manifests for ArgoCD Applications?▼

ConfigHub renders Kubernetes manifests for ArgoCD Applications using the ArgoCDRenderer bridge, creating wet Units that represent the rendered manifests for governance, before deploying them through ConfigHub's OCI-based flow.

What is the difference between dry Units and wet Units when importing ArgoCD into ConfigHub?▼

When importing ArgoCD into ConfigHub, dry Units represent the ArgoCD Application resource itself, while wet Units represent the fully rendered Kubernetes manifests, enabling comprehensive discovery and governance across a single workflow.