migrate-from-kubectl

To find manually modified Kubernetes resources before moving to GitOps, you need to inspect managedFields for human authorship. This Skill detects candidate resources whose last writer is a kubectl-* manager and classifies them as human-edited rather than controller-owned.

The best way to plan a migration from kubectl apply to GitOps without mutating the cluster is to run read-only scanning workflows. This Skill generates inventory, decisions, and baselines via snapshotting and import-preview guidance without altering live state.

To prioritize which Kubernetes workloads to migrate to GitOps first, you need a risk-ranked backlog based on operational context. This Skill uses scanning to prioritize resources by severity, helping you decide whether to revert, port to git, or accept as canonical.

GitOps migration does require understanding managedFields to track kubectl drift, as these fields indicate human authorship. This Skill uses managedFields metadata to identify kubectl-touched resources and produce migration evidence via receipt verification for safe cluster-wide adoption.

You can preview importing existing Kubernetes configurations into a GitOps repository using read-only import-preview paths. This Skill optionally snapshots current state and previews the import-to-repo path to help teams safely port resources to git.

Kubernetes resources drift from your GitOps source of truth after legacy operations because of ad-hoc kubectl apply or edit activity. This Skill identifies those manually touched resources and turns them into a per-resource transition plan to stop drift.