AWS Builder Center

Road to Kubestronaut Ep. 1: Preparing for the CKA with AWS

CKA preparatios and K8s learning through : Amazon EKS and Kubernetes clusters that I bootstrapped myself on EC2 instances

I’m starting a new learning journey toward becoming a Kubestronaut.
The first milestone is the CKA [I got it btw] .
For my CKA preparation, I’ve been working with Kubernetes in two different environments: Amazon EKS and Kubernetes clusters that I bootstrapped myself on EC2 instances. i tried multiple approaches of infra provisioning through terraform and by hand in AWS UI .
I found that using both gives me a much better understanding of Kubernetes.

Learning Kubernetes with EKS

Amazon EKS is a great way to get a Kubernetes cluster running without having to manage every part of the control plane yourself.
It lets me focus on the Kubernetes side of things:
kubectl get nodes
kubectl get pods -A
kubectl get svc
kubectl describe pod <pod>
kubectl get events

From there, I can work on the things that actually matter for the CKA:
• Deployments and Pods • Services and networking • RBAC • Storage • Scheduling • Taints and tolerations • NetworkPolicies • Troubleshooting • Resource requests and limits
EKS also gives me the opportunity to see how Kubernetes interacts with AWS.
For example, I can work with AWS networking, load balancers, IAM, EBS, EFS, ECR and other AWS services alongside Kubernetes.
That makes the learning much closer to how Kubernetes is used in real environments.

Then I wanted to understand what EKS hides

EKS handles a lot of the control plane management for you.
That's convenient, but when preparing for the CKA, I also wanted to understand what actually happens underneath Kubernetes.
So I started building Kubernetes clusters myself using EC2 instances.
Instead of starting with an already working cluster, I had to deal with things like:
• Setting up the nodes • Installing the container runtime • Configuring kubeadm • Setting up the control plane • Joining worker nodes • Configuring the CNI • Understanding certificates • Understanding etcd • Troubleshooting kubelet • Fixing networking issues • Dealing with DNS problems
This was probably one of the most useful parts of my preparation.
When something breaks in a self bootstrapped cluster, there isn't much to hide behind.
If the kubelet isn't working, you have to figure out why.
If the CNI is broken, you have to understand what it is doing.
If a node can't communicate with the API server, you need to troubleshoot the actual problem.

EKS + self managed clusters

I don't see these as competing approaches.
They complement each other.
EKS gives me experience operating Kubernetes in a managed cloud environment.
Self bootstrapping Kubernetes on EC2 forces me to understand the components underneath it.
Together, they give me a much better mental model of Kubernetes.
For example, when I run:
kubectl get pods

I'm not just thinking about the command anymore.
I'm thinking about the API server, authentication, the scheduler, kubelet, the container runtime and the networking layer behind that Pod.
That understanding is what I'm trying to build for the CKA.

How I'm approaching the CKA

I'm trying not to treat the CKA as a list of commands to memorize.
My approach is:
Learn → Build → Break → Troubleshoot → Repeat
For each topic, I try to understand the concept first, implement it on a cluster, break it intentionally, and then troubleshoot it.
For example, instead of only learning how to create a NetworkPolicy, I'll create one, test the traffic, break it, and figure out why the traffic is being blocked.
The same goes for scheduling, networking, storage and RBAC.

What's next?

I'll be documenting the rest of the journey as I go, including the labs, problems I run into and things I learn along the way.
Some of the topics I'll cover:
• EKS networking • Kubernetes networking • RBAC and IAM • Storage • Scheduling • NetworkPolicies • Troubleshooting • Cluster administration • CKA practice labs • Terraform and EKS
The goal isn't just to pass the CKA.
I want to actually understand Kubernetes well enough to operate and troubleshoot it.
That's the first step on my Road to Kubestronaut.
#AWS #EKS #Kubernetes #CKA #DevOps #CloudNative
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article