EKS 1.34 to 1.35 Upgrade — A Best-Practices-Driven Verification
Upgrading EKS following AWS best practices end-to-end: Cluster Insights, deprecated API scanning, PDB-backed availability guarantees, and post-upgrade validation.
Articles about cloud infrastructure, containers, IaC, and platform engineering
Upgrading EKS following AWS best practices end-to-end: Cluster Insights, deprecated API scanning, PDB-backed availability guarantees, and post-upgrade validation.
Create an ArgoCD Capability using eksctl's declarative YAML config and deploy a sample app. Covers the differences from AWS CLI and CloudFormation behavior.
Enable ArgoCD Capability on EKS via AWS CLI and deploy a sample app end-to-end. Covers real gotchas like Identity Center region mismatch and access policy setup.
Verified ClusterNetworkPolicy and ApplicationNetworkPolicy on EKS Auto Mode. Domain name-based egress filtering enables multi-layered access control that restricts pods to specific external services only.
Set up CloudWatch Vended Logs for EKS Auto Mode's 4 components (Compute/Block Storage/Load Balancing/IPAM) and analyze scale-up to scale-down behavior with Logs Insights queries.
Set up an EKS cluster with Auto Mode enabled using a single eksctl command. Covers how Auto Mode eliminates node group management and when to choose it over traditional managed node groups.