Discover how to build, deploy, scale, and manage Kubernetes. Gain insights into architecture, pods, deployments, services, and run real-world projects to solidify your skills.

kubernetes.tar.gz

kubernetes

port-30001

port-3000

port-4567

port-8001

Port-3001

Port-3001-v1

Kubernetes in Practice is your one-stop shop for learning how to build, deploy, scale, and manage Kubernetes in a step-by-step process.

You will learn all the most important concepts including: architecture, pods, deployments, services, ingress, and a whole lot more. Once you have the fundamentals out of the way, you will get the opportunity to put your skills to work in a project where you will create and run an application in a real Kubernetes cluster.

By the time you finish this course, you will have complete confidence when it comes to deploying and managing kubernetes clusters.

Kubernetes in Practice

When we create a pod to run our application, we can define how much CPU and memory it will need. Kubernetes will then only schedule this pod on nodes that have enough capacity to  fulfil these requests. 

This does not mean the containers will be limited to that amount of resources; it just means that if a node can't provide the requested CPU and memory, the pod won't even be allowed to run there.

Here's how we define this request in the pod's definition:

apiVersion: v1
kind: Pod
metadata:
  name: busybox
spec:
  containers:
  - name: busybox-container
    image: busybox
    command: ["dd", "if=/dev/zero", "of=/dev/null"]
    resources:
      requests:
        cpu: 500m
        memory: 5Mi

We're running a `busybox` container, which is a super small image that includes some useful UNIX utilities we can use. We define the command
`dd if=/dev/zero of=/dev/null`
as the container entrypoint. This is a command that won't really do anything useful, but it will use as much CPU as it can, so it works well for our tests.

We can also see a new attribute called `resources` where we define how much CPU and memory we need. We are saying we want 500 millicores (1/2 of a single CPU core) and 5 megabytes of memory.

Learn how we can define resources for our pods.

Before We Begin

What Kubernetes Brings to the Table

Kubernetes Architecture

Pods

Deployments

Services

Deploying a Web Application over Kubernetes

Ingress

Configuring Applications with Configmaps

Using Secrets for Sensitive Configs

Running Jobs

Fault-Tolerant Web Hosting on Kubernetes

Organizing Resources with Namespaces

Managing Containers Resource Usage

Understanding the Kubeconfig File

Kubernetes IRL

Appendix

Wrap Up!

Defining Resource Requests

Defining request