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

import-from-cluster

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Onboarding existing Kubernetes resources into ConfigHub when there is no GitOps source of truth, enabling centralized governance from ConfigHub.

Core Features & Use Cases

  • Import live cluster state as literal YAML into ConfigHub Units via cub unit import bound to a cluster Target.
  • Use preflight gates, dry-runs, and scoping filters to import only what you own and avoid drift.
  • Use Case: You have a payments namespace managed by kubectl; import its resources to manage them via ConfigHub without Helm/ArgoCD/Flux.

Quick Start

Create a Unit bound to your cluster Target and run a dry-run import to preview what will be captured.

Frequently Asked Questions about import-from-cluster

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

FAQPage Schema
How do I import existing Kubernetes resources into ConfigHub without a GitOps tool?▼

You import existing Kubernetes resources into ConfigHub by capturing the live cluster state as literal YAML. Using cub unit import bound to a cluster Target, the skill brings resources under centralized governance without needing Helm, ArgoCD, or Flux.

Can I filter which Kubernetes resources are imported by namespace or label?▼

Yes, you can filter imported Kubernetes resources by namespace, kind, or label. The skill applies --where-resource filters during the cub unit import process to scope the capture and avoid drift.

What do I need to set up before importing a live cluster into ConfigHub?▼

Before importing a live cluster into ConfigHub, you need a Kubernetes Target and a bound Worker. You create a Unit bound to that cluster Target to receive and mirror the literal YAML cluster state.

Does the ConfigHub import process support dry-runs to preview cluster state?▼

Yes, the ConfigHub import process supports dry-runs to preview cluster state. You run a dry-run import on a Unit bound to your cluster Target to preview exactly what resources will be captured before applying changes.

How does managing Kubernetes resources through ConfigHub compare to using kubectl directly?▼

Managing Kubernetes resources through ConfigHub differs from using kubectl directly by providing a centralized governance source of truth. ConfigHub imports live cluster state as literal YAML, enabling controlled management without manual kubectl operations.

Related Skills

Explore More Software Engineering Skills→
AsmayaseenAsmayaseen
2

deploying-postgres-k8s

Deploy PostgreSQL clusters on Kubernetes with CloudNativePG automated failover.

Community
Advanced
confighubconfighub
2

config-as-data

Store Kubernetes configuration as literal YAML in ConfigHub units via cub mutations.

Official
Advanced
ToanPV90ToanPV90

k8s-yaml-validator

Validate Kubernetes YAML manifests for syntax, schema, and dry-run errors.

Community
Advanced
mujezmujez
47

argocd-helm

Automate Kubernetes GitOps deployments with ArgoCD and Helm.

Official
Advanced