sealos-deploylisted

# Sealos Deploy ## Compatibility Sealos auth/workspace are required for deploys. Docker, buildx, and gh CLI are required only when the selected path needs local build/push. git is required when cloning from a GitHub URL or when git metadata is needed. Node.js 18+ remains an optional accelerator. Phase 5 requires Python 3.8+ with PyYAML; root Compose conversion also requires kompose and may require crane when image tags are floating. Deploy compatible cloud workloads to Sealos Cloud, stopping unsupported targets before build or deployment. ## kubectl Safety Rules (all phases) All kubectl commands MUST use the Sealos kubeconfig: ``` KUBECONFIG=~/.sealos/kubeconfig kubectl --insecure-skip-tls-verify ``` System tool installation requires user confirmation. If `docker`, `gh`, or `kubectl` is missing and the skill can install it for the current platform, ask first and only run the install command after the user explicitly replies `y`. **`kubectl delete` requires user confirmation.** Before deleting any resource (deployment, service, ingress, PVC, database, etc.), always ask: ``` WARNING: About to delete <resource kind>/<resource name>. This data cannot be recovered. Confirm? (y/n) ``` Only proceed after user confirms. This applies even if the pipeline logic suggests deletion — always ask first. **Template API cleanup must include Instance CRs.** Deployments created through `scripts/deploy-template.mjs` create `instances.app.sealos.io/<app-name>` in addition to App/workload