arc-terraform-deployment

What problem does it solve?

Deploying GitHub Actions Runner Controller (ARC) infrastructure with Terraform on Kubernetes can be tricky, especially when dealing with Custom Resource Definitions (CRDs) that are installed during the same terraform apply run. This often leads to "CRD not found" errors. This Skill provides robust Terraform patterns to overcome these challenges.

Core Features & Use Cases

• kubectl_manifest for CRDs: Uses the kubectl_manifest provider to apply ArgoCD Applications (CRDs) at runtime, avoiding plan-time validation failures.
• CRD Registration Wait: Incorporates time_sleep to ensure CRDs are fully registered with the Kubernetes API server before dependent resources are created.
• Namespace Ownership Strategy: Guides on letting ArgoCD manage namespaces to prevent conflicts with Terraform.
• Modular Deployment Patterns: Provides patterns for installing ArgoCD and deploying runner scale sets using Terraform modules and ApplicationSets.
• Use Case: When setting up a new Rackspace Spot Kubernetes cluster and deploying GitHub Actions ARC, use this Skill to correctly configure Terraform to install ArgoCD, wait for its CRDs to register, and then deploy the ArgoCD bootstrap Application, ensuring a smooth, automated infrastructure rollout.

Quick Start

Use the arc-terraform-deployment skill to explain why kubectl_manifest is preferred over kubernetes_manifest when deploying ArgoCD Applications with Terraform, and how time_sleep helps resolve CRD registration issues.