[NEW] Amazon EKS Starter: Docker on AWS EKS with Kubernetes

Explore the Amazon EKS architecture, seeing how AWS abstracts the control plane and etcd, enabling high availability across multiple availability zones while you focus on managing worker nodes.

EKS pricing overview highlights the cluster cost at about 10 USD per hour, with no free tier and fees for worker nodes, EC2, EBS, and load balancers.

Create a dedicated IAM user for the course with programmatic and console access, avoid the root account, and attach admin or granular policies; download and securely store the access keys.

Create an IAM role for Amazon EKS to manage clusters, then generate an EC2 key pair and create access keys, and securely save the credentials.

install and verify eksctl and kubectl across macOS, Linux, and Windows; configure credentials, set region, and test versions to prepare kubernetes on AWS EKS.

Create an EKS cluster with eksctl using a YAML config file and cloud formation templates, provisioning a VPC with subnets, security groups, and three t2.small worker nodes in us-west-2.

Scale a node group in an AWS EKS cluster with eksctl, adding a mix of on-demand and spot instances. Inspect the cluster to confirm node changes and pods relocation.

Add a mixed on-demand and spot node group to an EKS cluster using a configuration file, with 50/50 distribution and max size 5, then drain and delete to stop costs.

The cluster autoscaler scales node groups based on resources and requests, running as a deployment, and accounts for single or multi-AZs, stateful or stateless workloads, and node sizing.

Configure two dedicated EKS node groups—one single-AZ for stateful workloads and one multi-AZ, spot-based for stateless workloads—with scaling via a YAML file and kubectl, then prepare for the outer scaler.

Deploy the cluster autoscaler by applying the GitHub YAML, annotate for safe-to-evict false, verify Kubernetes version alignment, and update the image to 1.22.2 for the cluster.

Deploy, scale, and observe Engine X in a Kubernetes cluster by creating an Engine X deployment, adjusting replicas, and using the cluster autoscaler to add and remove spot instances.

Enable CloudWatch logging for EKS cluster services by selecting API audit and authenticator log types via eksctl config file. Monitor log groups and pricing, and disable logging when needed.

Explore the Helm package manager for Kubernetes, including charts, config files, and releases. Learn to install Helm, add repositories, search charts, and deploy a Redis example.

Learn to create an AWS IAM user with cluster admin privileges in EKS and a read-only user for a dedicated namespace, configuring access with credentials and kubectl.

Set up a read-only user in a production namespace by creating an IAM user, a read-only role and binding, and updating the config map; test access with kubectl.

Learn Amazon EKS pricing: about 0.10 per hour per cluster (roughly 73 dollars monthly) plus costs for workers, EBS, traffic, and load balancers; the control plane is managed by EKS.

Explore the Kubernetes control plane architecture across multiple availability zones with master nodes and etcd per zone, while provisioning and managing worker nodes in a single-tenant vpc environment.

Explore eks networking essentials, including vpc design with private and public subnets, cidr sizing, dns resolution, and security groups, plus pod networking with cni and ip per eni.

Learn how Kubernetes uses IAM for authentication and RBAC for authorization with AWS, enabling cluster access through IAM roles and config map updates.

Learn to configure Kubernetes load balancers in EKS using annotations and manifests, choosing classic, network, or application load balancers, including internal options and TLS support via the load balancer controller.

Explore the Kubernetes dashboard, a web-based UI to view clusters, pods, namespaces, and services, and learn to install it with kubectl and access via proxy using a token.

Deploy the Kubernetes dashboard with a single kubectl apply from the GitHub link, creating namespace, service account, config map, secrets, and deployment, then verify with kubectl get all.

Create a service account named course admin in the kube-system namespace and bind it to the cluster-admin role with a YAML file. Apply the resources and explore the Kubernetes dashboard.

Create a bearer token for a service account, start kubectl proxy, and log into the Kubernetes dashboard to view deployments, pods, and namespaces.

Deploy a stateless guest book php app on a Kubernetes cluster, exposed by an air base load balancer, and explore backend reads and writes via Redis.

Deploy the backend by creating a leader deployment and leader service, then add follower deployments and their services. Inspect the cluster network to verify pod connectivity and internal service endpoints.

Deploy the guest book frontend on Kubernetes with three replicas and a load balancer service, then access the app via the external DNS and submit entries.

Scale up and down pods in a Kubernetes deployment using kubectl, YAML edits, or the Kubernetes dashboard to manage replicas for a stateless front-end app.

Perform chaos testing to stress deployments, verify Kubernetes self-healing by killing pods and stopping worker nodes, and observe rapid pod and node recovery in a realistic EKS environment.

Learn how to perform a quick cleanup in Amazon EKS to reduce costs by deleting pods, deployments, and services, with an optional choice to leave resources running.

Deploy a stateful WordPress app with a MySQL backend on eks using ebs volumes and persistent volumes, then compare deployment versus stateful set and discuss availability zones constraints.

Create a namespace to separate workloads in Kubernetes for project, client, and team environments with resource quotas and access control, used for the WordPress stateful app.

Verify the default gp2 storage class in Kubernetes, then create persistent volume claims for MySQL and WordPress. Learn about the volume binding mode wait for first consumer and EBS provisioning.

Deploy the MySQL backend by creating a secret, deploying a MySQL pod and service, and attaching it to an EBS persistent volume, then verify via kubectl and the Kubernetes dashboard.

Explore deployment versus statefulset in Kubernetes on AWS EKS, and learn how persistent volumes with EBS affect pod attachment and data accessibility for apps like WordPress.

Deploy WordPress via a Kubernetes deployment behind a load balancer, using persistent volumes for WordPress and MySQL, then scale from 1 to 2 pods and verify via the dashboard.

Deploy WordPress using a stateful set with per-pod persistent volumes and a load-balanced service, then scale to pods while noting each pod has its own volume and shared MySQL backend.

Delete the WordPress frontend, MySQL backend, and EBS volumes on Kubernetes to clean up costs. Use YAML to delete deployments, stateful sets, services, and PVCs, then verify a clean state.