Deploying workloads on EKS in AWS - Step-by-Step Execution

Process Flow - Deploying workloads on EKS

Create EKS Cluster

↓

Configure kubectl

↓

Write Deployment YAML

↓

Apply Deployment

↓

Pods start running

↓

Verify workload status

↓

Done

This flow shows the steps to deploy an application on EKS: create cluster, configure access, write deployment, apply it, pods run, verify.

Execution Sample

AWS

eksctl create cluster --name my-cluster --region us-west-2
aws eks --region us-west-2 update-kubeconfig --name my-cluster
kubectl apply -f deployment.yaml
kubectl get pods

Creates an EKS cluster, configures kubectl, deploys a workload using a YAML file, then checks pod status.

Process Table

Step	Action	Command/Description	Result/State
1	Create EKS Cluster	eksctl create cluster --name my-cluster --region us-west-2	Cluster 'my-cluster' created and ready
2	Configure kubectl	aws eks --region us-west-2 update-kubeconfig --name my-cluster	kubectl configured to access cluster
3	Write Deployment YAML	deployment.yaml with container image and replicas	Deployment manifest ready
4	Apply Deployment	kubectl apply -f deployment.yaml	Deployment created, pods starting
5	Pods start running	kubectl get pods	Pods in Running state
6	Verify workload	kubectl describe deployment my-app	Deployment ready with desired replicas
7	Exit	All pods running and workload deployed	Deployment successful, process complete

💡 All pods are running and deployment is successful, so deployment process ends.

Status Tracker

Variable	Start	After Step 1	After Step 4	After Step 5	Final
Cluster State	None	Created	Created	Created	Created
kubectl Config	None	Configured	Configured	Configured	Configured
Deployment Status	None	None	Created	Pods Running	Pods Running
Pods State	None	None	None	Running	Running

Key Moments - 3 Insights

Why do we need to configure kubectl after creating the cluster?

kubectl needs cluster access info to communicate with EKS. Step 2 shows configuring kubectl after cluster creation.

What happens if pods do not reach Running state after applying deployment?

Pods may be pending or failing. Step 5 shows pods starting; if not Running, check pod logs or events.

Why is writing a deployment YAML important before applying?

Deployment YAML defines what to deploy and how. Step 3 prepares this manifest, which kubectl uses in Step 4.

Visual Quiz - 3 Questions

Look at the execution table, what is the cluster state after Step 1?

A Configured

B None

C Created

D Running

💡 Hint

Check the 'Cluster State' variable in variable_tracker after Step 1.

At which step do pods start running?

A Step 3

B Step 5

C Step 4

D Step 2

💡 Hint

Look at the 'Pods State' variable in variable_tracker and the execution_table rows.

If kubectl is not configured, what will happen when applying deployment?

A kubectl cannot connect to cluster, deployment fails

B Deployment applies successfully

C Pods start running anyway

D Cluster is automatically configured

💡 Hint

Refer to Step 2 and Step 4 in execution_table and kubectl Config variable in variable_tracker.

Concept Snapshot

Deploying workloads on EKS:
1. Create EKS cluster (eksctl).
2. Configure kubectl to access cluster.
3. Write deployment YAML with app details.
4. Apply deployment with kubectl.
5. Pods start running and workload is live.
Always verify pod status after deployment.

Full Transcript

To deploy workloads on EKS, first create a cluster using eksctl. Then configure kubectl to connect to the cluster. Next, write a deployment YAML file describing your application and how many replicas you want. Apply this deployment using kubectl apply. The pods will start running in the cluster. Finally, verify the pods are running and the deployment is ready. This process ensures your application runs on the managed Kubernetes cluster.