What problem does it solve?
Setting up a PAIDF Orchestration environment requires auditing GPU capacity, resolving kubeconfig access, validating secrets, deploying an Airflow controller via Helm, and verifying controller readiness — a multi-step process where mistakes like pre-creating Helm-managed secrets or using unreachable kubeconfig server addresses cause hard-to-diagnose failures.
Core Features & Use Cases
- Read-only cluster audit: Runs
scripts/remote_k8s.py audit locally or over SSH to report GPU capacity, namespace, registry secret, and storage class readiness as structured JSON without mutating the cluster.
- Guided controller deployment: Walks through
make setup (secrets validation and Helm values generation) and make install sdg-controller, with explicit approval gates, S3 connectivity pre-flight, and post-install verification against live cluster state.
- Topology and service-mode selection: Helps choose controller placement and external versus in-cluster model services independently, recommending external endpoints for single-GPU H100 nodes.
- Use Case: A user with one H100 host running k3s asks to set up SDG Workflow; the skill audits the cluster over SSH, recommends external model endpoints, validates
secrets.env, deploys the Airflow controller, and verifies pools, DAGs, and connections before reporting readiness.
Quick Start
Ask the agent to audit your GPU cluster for PAIDF Orchestration and provide the path to your kubeconfig when prompted.