osdc-deployment

Deploy and operate OSDC Kubernetes clusters on AWS EKS with Terraform and Helm.

17|14|Updated Jun 15, 2023
One-click install
npx skills add https://github.com/pytorch/ci-infra --skill osdc-deployment
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: osdc-deployment
Source: https://github.com/pytorch/ci-infra/tree/main/osdc/.claude/skills/osdc-deployment
Command: npx skills add https://github.com/pytorch/ci-infra --skill osdc-deployment

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a consistent, validated workflow for deploying, testing, troubleshooting, and operating OSDC Kubernetes clusters on AWS, reducing configuration mistakes and deployment risk.

Core Features & Use Cases

  • Deployment Workflows: Guides base infrastructure, module deployment, Terraform state, Helm, Kubernetes manifests, and cluster-specific configuration driven by clusters.yaml.
  • Operational Guardrails: Enforces kubeconfig locking, deployment confirmations, node draining and tainting, smoke tests, audit tracking, and safe recovery procedures.
  • Validation and Troubleshooting: Covers linting, unit and integration tests, smoke testing, ARC runner health, capacity analysis, cluster recreation, and common Terraform or Kubernetes failure modes.
  • Use Case: Use this Skill to add a module to a cluster, deploy it in the correct order, run the required validation, and diagnose issues without bypassing repository deployment conventions.

Quick Start

Use the osdc-deployment skill to inspect a cluster configuration and provide the safest commands to deploy or troubleshoot the requested OSDC change.

Frequently Asked Questions about osdc-deployment

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy an AWS EKS cluster using Terraform and Helm with consistent configuration?

AWS EKS cluster deployment with Terraform and Helm requires a clusters.yaml-driven orchestration workflow that applies ordered base infrastructure and module changes, enforces kubeconfig locking, and runs validation smoke tests to ensure safe configuration.

What is the safest way to add a new module to an existing Kubernetes cluster deployment?

Adding a module to a Kubernetes cluster deployment safely requires following ordered deployment conventions, applying Terraform state changes, running required validation tests, and generating audit records without bypassing repository deployment guardrails.

Can I use GitHub Actions runners for smoke testing OSDC Kubernetes clusters?

GitHub Actions runners support smoke testing OSDC Kubernetes clusters by validating ARC runner health, performing capacity analysis, and running integration tests to verify cluster infrastructure before completing deployment operations.

Why does my Terraform deployment fail during node lifecycle operations on AWS EKS?

Terraform deployment failures during node lifecycle operations often stem from improper node draining and tainting, bypassing deployment confirmations, or missing operational safety controls required for AWS EKS cluster recreation and recovery.

Do I need locked kubeconfig updates to troubleshoot Kubernetes cluster configuration issues?

Locked kubeconfig updates are required to safely troubleshoot Kubernetes cluster configuration issues, ensuring deployment confirmations, audit tracking, and safe recovery procedures are followed during cluster recreation and operational changes.

What's the best way to run validation tests after deploying Helm charts to a Kubernetes cluster?

Running validation tests after deploying Helm charts involves executing linting, unit tests, integration tests, and smoke testing to verify Kubernetes manifests, Helm configurations, and Terraform state before finalizing cluster deployment operations.