arc-terraform-deployment

CRD not found errors occur when Terraform attempts to create resources that depend on Custom Resource Definitions installed during the same apply run. The kubectl_manifest provider defers validation until runtime, allowing CRDs to register with the API server before dependent resources are created, preventing this failure.

Use Terraform modules to install ArgoCD via kubectl_manifest, add explicit time_sleep waits for CRD registration, then deploy runner scale sets through ArgoCD ApplicationSets. This pattern coordinates CRD availability, ArgoCD bootstrap, and namespace management across create-time dependencies to ensure smooth automated rollout.

kubectl_manifest is preferred for ArgoCD Applications because it applies resources at runtime, avoiding plan-time validation failures when CRDs don't exist yet. The kubernetes_manifest provider validates at plan time, which fails if CustomResourceDefinitions haven't been registered.

Incorporate time_sleep to ensure CRDs are fully registered with the Kubernetes API server before creating dependent resources. Combine this with kubectl_manifest for ArgoCD Applications and let ArgoCD manage namespaces to prevent sync conflicts between Terraform and ArgoCD.

Yes, this Skill provides Terraform patterns specifically for deploying ARC infrastructure on Rackspace Spot Kubernetes. It handles CRD registration, ArgoCD installation, and namespace ownership strategy to automate the entire workflow without manual intervention or synchronization conflicts.

Let ArgoCD manage namespaces and use Terraform only for installing ArgoCD and registering CRDs. This division prevents sync conflicts and allows ArgoCD to handle GitOps-driven deployments while Terraform manages the bootstrap infrastructure layer.