osdc-runners-nodepools

To prevent configuration drift when modifying GitHub Actions runners and EKS NodePools, synchronize generator inputs, instance specifications, workload mappings, labels, and integration workflow markers before applying mandatory lint, test, and utilization validation.

When adding a new EC2 instance type to Kubernetes runner infrastructure, you must update runner definitions, node pools, instance specifications, sizing tables, taints, labels, workflow references, and naming documentation consistently to avoid deployment failures.

BuildKit NUMA placement and Karpenter node compaction in OSDC environments require synchronized architecture-specific scheduling constraints and startup taints to maintain operational reliability and prevent workload scheduling conflicts during infrastructure troubleshooting.

Yes, this approach supports IPv6-only EKS networking, ARC hooks, DaemonSet overhead, image mirroring, and cache enforcement by applying required resource-sizing, taint, and scheduling checks tailored for production CI infrastructure.

GitHub Actions workflow label changes cause deployment failures across node pools when generator inputs, integration workflow markers, and architecture-specific scheduling constraints are not synchronized with the updated runner definitions and node pool configurations.

The best way to validate runner infrastructure changes before production deployment is to run mandatory lint, test, utilization-analysis, generator, taint, resource-sizing, and scheduling checks to ensure all definitions and mappings are synchronized.