<p>If you are a developer, system administrator, or solution architect who wants to make the transition into Kubernetes an absolute breeze, this book is your key to success.</p>

Start Kubernetes

This book is a mix of theoretical explanations and practical examples. You’ll get the most out of this book if you follow along with the practical examples. To do that, you will need the following tools:

Docker Desktop Access to a Kubernetes cluster, see Which Kubernetes cluster should I use? Kubernetes CLI ( kubectl ) 

For some sections, you might also need other tools that I mention in the specific chapters.

What do I need to start with Kubernetes?

Preface

You have multiple choices. The most 'real-world' option would be to get a Kubernetes cluster from one cloud provider. However, for numerous reasons, that might not be an option for everyone.

Which Kubernetes cluster should I use?

After you’ve installed one of these tools, make sure you download the Kubernetes CLI . Kubernetes CLI is a single binary called kubectl , and it allows you to run commands against your cluster. To make sure everything is working correctly, you can run kubectl get nodes to list all nodes in the Kubernetes cluster. The output from the command should look like this:

Kubernetes and contexts

Containers are everywhere these days. People use tools such as Docker for packaging anything from applications to databases. With the growing popularity of microservice architecture and moving away from the monolithic applications, a monolith application is now a collection of multiple smaller services.

What is container orchestration?

A Kubernetes cluster is a set of physical or virtual machines and other infrastructure resources needed to run your containerized applications. Each machine in a Kubernetes cluster is called a node . There are two types of node in each Kubernetes cluster:

Kubernetes architecture

The Kubernetes API defines many objects called resources, such as namespaces, pods, services, secrets, config maps, etc.

Kubernetes Resources

One of the factors from the Twelve-Factor App manifesto talks about application configuration, specifically about storing configuration in the environment, instead of hardcoding it inside your services.

Configuration

Running stateful workloads inside Kubernetes is different from running stateless services. The reason being is that the containers and Pods can get created and destroyed at any time. If any of the cluster nodes go down or a new node appears, Kubernetes needs to reschedule the Pods.

Stateful Workloads

Organizing Containers

The kubelet component in Kubernetes uses different health checking mechanisms to verify if the containers inside your Pods have started (startup probe), are ready to receive traffic (readiness probe), and are healthy (liveness probe).

What do I need to start with Kubernetes?

Community Questions