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