import-from-kustomize

You can import Kustomize overlays into ConfigHub by rendering them locally with kustomize build, validating the output, and persisting the results as Units using cub unit create. This process preserves lineage and enables per-environment management within ConfigHub.

Rendering Kustomize overlays locally before storing them as Units eliminates the error-prone manual management of base and overlay trees. It attaches a change-desc for clear lineage and enables downstream mutation via cub-mutate for per-environment customization within ConfigHub.

Yes, you can use cub-mutate for per-env customization after importing Kustomize overlays. The skill creates per-environment Units that mirror space topology, explicitly enabling downstream mutation workflows for targeted environment-specific modifications.

Yes, importing Kustomize overlays requires a local rendering environment because the skill explicitly executes kustomize build locally to render the base and overlay trees. The validated output is then ingested into ConfigHub as Units.

The best way to manage Kustomize base and overlay trees for governance is to render them locally and ingest the output into ConfigHub as Units. This approach replaces manual management with structured per-environment Units supporting upgrades, rollbacks, and audits.