Skip to content

Operations Guide ​

Last Updated: September 12, 2026

This section provides a production operations guide for EKS Auto Mode environments. It covers infrastructure provisioning with Terraform, CI/CD pipelines, GitOps-based deployment, scaling, observability, resource optimization, and upgrades.


Target Audience ​

  • Platform Engineers building production environments with EKS Auto Mode
  • Infrastructure Engineers operating Terraform/Terragrunt-based IaC
  • DevOps Engineers building CI/CD pipelines with GitLab CI and ArgoCD
  • SREs operating Prometheus, Grafana, and Loki observability stacks

Prerequisites ​

Before starting this operations guide, ensure familiarity with:


Table of Contents ​

#DocumentKey Topics
01Terraform 3-Layer Infrastructure SetupVPC, EKS Auto Mode, Pod Identity with 3-Layer Terraform
02NLB Weighted Routing and Blue/GreenDual cluster architecture, NLB weights, DNS routing
03CI PipelinesECR, GitLab Runner, GitHub ARC, multi-platform builds
04ArgoCD Multi-ClusterHub-spoke, ApplicationSet, IAM Identity Center SSO
05GitOps AutomationAtlantis, FluxCD, Terraform Cloud, AIOps
06Scaling StrategiesHPA custom metrics, KEDA, VPA, Spot utilization
07Operational Alert ConfigurationNetwork/CPU/Disk/Auto Mode node termination alerts
08Observability AnalysisLogs/Metrics/Traces correlation, PromQL, LogQL, TraceQL
09Observability Stack OperationsLoki, Tempo, Prometheus/AMP installation and operations
10Resource OptimizationRequests/Limits, JVM tuning, framework-specific guide
11EKS UpgradesStaged Auto Mode upgrade, blue/green strategy
12Event Capacity PlanningTraffic events, capacity and recovery planning
13FinOps Cost ManagementCost visibility, allocation, optimization
14Tekton PipelinesKubernetes-native CI pipelines
15Zonal Cluster OperationsLB weight shifting and TargetGroupBinding, native rollback, Kafka/Redis/Aurora AZ-affine reads
16Troubleshooting PlaybookSymptom → diagnosis → cause → fix: Pending/ImagePull/CrashLoop/NotReady/PVC, IRSA, VPC CNI, Karpenter, kubectl cheat sheet
17EKS Spot Production ExperimentsInterruption, concurrent reclamation, fallback, result records, SLO/cost assessment, rollback

Learning Path ​

  1. Infrastructure (01-02): Provision VPC/EKS with Terraform
  2. CI/CD (03-05): Build pipelines and GitOps deployment
  3. Scaling (06): Establish scaling strategies for workloads
  4. Observability (07-09): Build monitoring, alerting, and analysis systems
  5. Optimization (10): Resource efficiency and cost optimization
  6. Upgrades (11): Validate availability and recovery procedures
  7. Specialized operations (12–16): Capacity events, FinOps, Tekton, zonal operations, and troubleshooting

By Role ​

RolePriority Documents
Platform Engineer01, 02, 04, 11
DevOps Engineer03, 04, 05
SRE06, 07, 08, 09, 10
Infrastructure Engineer01, 02, 11

Relationship with Existing Documentation ​

This operations guide complements existing concept documentation with practical, code-focused guides:

Concept Documentation ​

This Operations Guide ​

  • Terraform HCL code for production infrastructure
  • YAML manifests for Kubernetes resources
  • PromQL/LogQL queries for observability
  • Bash scripts for operational automation
  • Step-by-step procedures with validation

Quick Reference ​

Common Operations ​

TaskDocumentSection
Create new EKS cluster01-infrastructure-setup3-Layer Terraform
Add new application to ArgoCD04-gitops-multi-clusterApplicationSet
Configure HPA with custom metrics06-scaling-strategiesCustom Metrics
Set up alerting for new service07-observability-alertsAlert Rules
Upgrade EKS version11-upgrade-operationsAuto Mode Upgrade

Emergency Procedures ​

ScenarioDocumentSection
Rollback deployment04-gitops-multi-clusterRollback
Rollback EKS upgrade11-upgrade-operationsNative rollback eligibility or blue/green failback
Adjust capacity after checking demand and availability06-scaling-strategiesCapacity and scaling policy
Debug failing pods16-troubleshooting-playbookSymptom-based diagnosis

Contributing ​

When adding new operational procedures:

  1. Include practical code examples (Terraform, YAML, bash)
  2. Provide validation steps for each procedure
  3. Document rollback procedures where applicable
  4. Add relevant PromQL/LogQL queries for monitoring
  5. Cross-reference related concept documentation