AWS EKS - KodeKloud Course Notes

Scope

The supplied URL is a course index with 33 lessons across nine sections. This archive synthesizes the index and the 12 linked lessons listed below. It is not a transcript or a claim to have reviewed all lessons. The remaining curriculum includes IPv6, Fargate, node groups, load balancers, Gateway API, VPC Lattice, and security groups for Pods; these are discovery pointers, not detailed findings from this ingest.

Synthesis

Amazon Elastic Kubernetes Service (EKS) separates AWS-managed control-plane operations from application and data-plane operations. AWS runs the core Kubernetes control-plane services. Operators still make decisions about compute, workload permissions, networking, add-ons, and application availability. Managed infrastructure reduces host-level maintenance; it does not remove the need to design and validate the surrounding system.

The networking material makes IP capacity an explicit scaling constraint. AWS VPC CNI assigns Pod addresses through node-attached Elastic Network Interfaces (ENIs), rather than generally assigning one ENI per Pod. In the IPv4 prefix-delegation model, an ENI secondary slot can hold a /28 block with 16 addresses. Warm address pools reduce allocation delays but reserve subnet capacity. Prefix delegation requires available contiguous blocks and does not remove other node or scheduling limits.

NetworkPolicy support also requires active enforcement. The course inspects the VPC CNI network-policy agent and tests default-deny egress. Its failed curl example reports DNS resolution failure. The practical lesson is to test name resolution and application connectivity separately, not treat one failed request as complete firewall validation.

Identity has two distinct directions. Operator cluster access uses IAM-backed authentication and cluster-access configuration, with the course contrasting native EKS access APIs against legacy aws-auth mappings. Workload access to AWS services uses mechanisms such as IAM Roles for Service Accounts (IRSA) or EKS Pod Identity. Neither direction substitutes for Kubernetes RBAC. Pod Identity’s managed associations and node agent differ from IRSA’s OIDC federation and annotations.

Karpenter provisions EC2 capacity for unschedulable workloads. It complements replica scaling rather than replacing it. Resource requests, disruption budgets, topology constraints, and storage placement determine whether provisioning and consolidation preserve availability. EBS provides AZ-bound block storage; EFS provides shared filesystem storage with its own mount connectivity and permission requirements. CSI drivers connect these services to Kubernetes volume abstractions.

External secret stores can supply mounted files or synchronized Kubernetes Secrets. Credential rotation, refreshed mounted content, and application reload are separate events. Monitoring likewise needs separate control-plane, node, Fargate, and application collection paths. Finally, an EKS control-plane upgrade is not a complete cluster upgrade: compute, add-ons, API compatibility, and workloads require separate checks and rollout plans.

Reliability Notes

Treat this as tutorial evidence, not current AWS compatibility documentation. Official AWS documentation requests timed out during this ingest. Omitted questionable Pod Identity CLI/environment-variable examples, precise control-plane topology claims, blanket public-endpoint assumptions, managed-control-plane etcd backup instructions, and unsupported pricing or automatic-upgrade guarantees. No deployment commands were executed.

Reviewed Lessons

• Architecture: https://notes.kodekloud.com/docs/AWS-EKS/EKS-Fundamentals/Architecture/page.md
• Prefix Delegation: https://notes.kodekloud.com/docs/AWS-EKS/EKS-Networking/Prefix-Delegation/page.md
• Network Policies: https://notes.kodekloud.com/docs/AWS-EKS/EKS-Networking/Network-Policies/page.md
• Cluster Access: https://notes.kodekloud.com/docs/AWS-EKS/Redundancy-Resiliency/Cluster-Access/page.md
• Pod Identity: https://notes.kodekloud.com/docs/AWS-EKS/Redundancy-Resiliency/Pod-Identity/page.md
• Karpenter: https://notes.kodekloud.com/docs/AWS-EKS/Compute-Scaling/Karpenter/page.md
• EBS: https://notes.kodekloud.com/docs/AWS-EKS/EKS-Storage/EKS-EBSElastic-Block-Store/page.md
• EFS: https://notes.kodekloud.com/docs/AWS-EKS/EKS-Storage/EKS-EFSElastic-File-System/page.md
• Secrets Options: https://notes.kodekloud.com/docs/AWS-EKS/EKS-Secrets/Kubernetes-Secrets-Options/page.md
• Monitoring: https://notes.kodekloud.com/docs/AWS-EKS/Upgrades-and-Maintenance/EKS-monitoring/page.md
• Upgrades: https://notes.kodekloud.com/docs/AWS-EKS/Upgrades-and-Maintenance/EKS-Upgrades/page.md
• Add-ons: https://notes.kodekloud.com/docs/AWS-EKS/Upgrades-and-Maintenance/EKS-Addon/page.md

See Also

Wiki Concepts

• Amazon EKS - Managed Kubernetes overview and decision map.
• Kubernetes Architecture - Managed-control-plane responsibility boundary.
• Kubernetes CNI - ENIs, warm pools, and IPv4 prefix delegation.
• Kubernetes Network Policies - Enforcement and DNS-aware validation.
• Authentication and Authorization - Operator access versus workload identity.
• Kubernetes Service Account - IRSA versus Pod Identity.
• Kubernetes Autoscaling - Karpenter capacity provisioning.
• Kubernetes Storage - EBS and EFS choices.
• ConfigMaps and Secrets - External stores and rotation boundaries.
• Logging and Monitoring - Separate telemetry paths.
• Cluster Upgrades - EKS compute and add-on lifecycle.
• Kubernetes Index - Domain navigation.

Related Sources

• CKA CNI lesson - Provider-neutral networking foundation.
• CKA ServiceAccount and RBAC lesson - Kubernetes identity foundation.
• CKA kubeadm upgrade lesson - Contrast self-managed and managed upgrades.

Creator / Entity

KodeKloud publishes the linked course notes. No existing KodeKloud entity page was identified during this ingest.