Inside
When I first started studying Kubernetes (K8s), I had no idea what it was or what it was used for. I'm now fully digging into Kubernetes and learning it step by step. Through this series I'll keep sharing my progress - its features, security issues, and most importantly, real-world remediations.
This post is written from a beginner's point of view, for people who are new to Kubernetes and want to understand it in simple terms.
Feeling lost when starting Kubernetes
When I heard the word Kubernetes for the first time, it honestly felt confusing. People were talking about clusters, pods, nodes and orchestration, and none of it made sense. I kept asking one simple question: why do we even need Kubernetes?
I already knew how applications run on servers - you deploy code, start a service, and hope everything keeps running. But as applications grow, problems appear. Servers crash, traffic increases, deployments become risky, and security is often ignored. This is where Kubernetes becomes useful.
What is Kubernetes in simple terms?
Kubernetes is an open-source container orchestration platform used to deploy, manage and scale containerised applications. Instead of manually managing servers and services, Kubernetes automates most operational tasks.
You tell Kubernetes what you want - such as how many copies of your application should run - and it ensures that state is always maintained. If a container crashes, it replaces it. If traffic increases, it scales the application. If a node fails, workloads are moved automatically.
Core components, explained simply
- Cluster - a group of machines that run your applications.
- Node - a single machine inside the cluster.
- Pod - the smallest deployable unit, where containers run.
- Container - the runtime environment that holds your application code.
You don't manage containers directly in Kubernetes. You manage pods, and Kubernetes handles everything underneath.
Why Kubernetes is used in production
- Ensures high availability of applications
- Automatically handles scaling based on demand
- Makes deployments and rollbacks safer
- Provides consistency across environments
From a security perspective, this also introduces new risks - misconfigured clusters, exposed services, weak RBAC permissions and insecure container images are all common in real environments.
What this series will cover
- Kubernetes architecture and features
- Common Kubernetes security issues
- Real-world attack scenarios
- Practical and realistic security remediations
This isn't about theory. It's about learning Kubernetes by doing - making mistakes, fixing them, and sharing those lessons openly. If you're also starting your Kubernetes journey, this series is for you.
Final thoughts
Kubernetes can feel complex at the beginning, but once the basics start making sense, everything builds naturally. This post marks the start of my Kubernetes learning and security journey, and I'll keep updating it with real examples and hands-on insights.
FAQ
What is Kubernetes in simple terms?
Kubernetes is an open-source system that runs and manages containers across a group of machines. You declare the state you want, say three copies of an app, and it keeps things that way, restarting or rescheduling containers when something fails.
Why do people use Kubernetes?
Because running containers by hand does not scale. Kubernetes handles scheduling, self-healing, scaling and networking for you, so the same setup runs on one laptop or a hundred servers without rewriting how you deploy.
Is Kubernetes hard to learn as a beginner?
It has a steep start because of the jargon, but the core idea is simple: declare what you want, let the cluster reconcile to it. Learning one piece at a time, pods then nodes then the control plane, makes it click.
Related reading
- Topic 2: How Kubernetes works (how the pieces actually run)
- Topic 3: Nodes, workloads and foundations (nodes, pods and namespaces)
- Topic 4: The 4Cs of cloud native security (where security fits in)
- Browse the whole Kubernetes Journey