CAST AI Observation-First Onboarding

Overview

Connect one approved cluster with the recommended castctl path, keep optimization automation off initially, and prove identity, telemetry, ownership, and rollback before expanding control.

Prerequisites

• A named kube context for EKS, GKE, AKS, or a supported CAST AI Anywhere environment
• Cluster-admin access for installation and reviewed least-privilege cloud permissions
• metrics-server when Workload Autoscaling will be evaluated
• An owner, maintenance window, rollback decision, and evidence location

Instructions

Step 1: Establish ownership

Use Read and Grep to locate existing CAST AI, autoscaler, Terraform, Helm, and GitOps definitions. Stop if another controller owns node provisioning or workload HPA behavior and no coexistence decision exists.