Agent skill · software engineering · jeremylongshore
castai-upgrade-migration
Upgrade the CAST AI umbrella chart or migrate standalone releases with preserved values, explicit downtime, staged verification, and recovery evidence. Use when performing component updates, GitOps adoption, or consolidation with castctl. Trigger with: "upgrade CAST AI", "migrate CAST AI Helm releases", "move CAST AI to the umbrella chart".
Why this skill is useful
Adds executable scripts for upgrading and validating CAST AI components that are not found in public documentation.
What it needs
Requires helm, jq, kubectl, terraform installed locally. Requires castai account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
CAST AI Upgrade and Umbrella Migration Overview Inventory the installed topology, pin the target, preserve values, and rehearse recovery before changing a cluster. Treat standalone-to-umbrella consolidation as a downtime-bearing migration, not an ordinary chart bump. Prerequisites Exact kube context, installation owner, current releases, chart/provider locks, and target Maintenance window, workload and platform owners, rollback threshold, and evidence path Current backups of declared values and infrastructure state references without secret material Instructions Step 1: Classify the installation Use Bash(helm:\) to determine whether the namespace has one castai umbrella release or multiple standalone releases. Use Read and Grep to map Terraform, GitOps, console, and castctl ownership. Do not proceed while authorities conflict. Step 2: Capture the baseline Use Bash(kubectl:\) for component images, readiness, recent warning events, policy-visible workload health, PDBs, HPAs, and pending pods. Record selected umbrella mode and optional component overrides. Step 3: Review target and render Pin the target chart or provider from current release metadata. Use Bash(helm:) to render the proposed umbrella values and Bash(terraform:) to save a reviewed plan when Terraform owns delivery. Inspect CRDs, RBAC, webhooks, component modes, removed values, and automation changes. Step 4: Choose upgrade or migration For an existing umbrella release, use the documented chart upgrade with --reset-then-reuse-values; Helm 3.14 or newer is required. Pin the current chart version when changing configuration without changing components. For standalone releases, use Bash(castctl:\) with cluster migrate; expect a window where components and both autoscalers are paused. Step 5: Protect recovery Before standalone migration, set and protect the values-dump destination. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/castai-upgrade-migration