<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>:: Kubernetes Labs</title><link>https://kubernetes.idsc.arch.cloud/index.html</link><description>Welcome These are the hands-on labs of the Kubernetes training. The theory is covered in the presentation, and here you put it into practice.
You start with your first Pod on a local k3s cluster and finish with your own Python application and a PostgreSQL database, deployed with plain manifests and packaged as a Helm chart.</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://kubernetes.idsc.arch.cloud/index.xml" rel="self" type="application/rss+xml"/><item><title>1. Setup</title><link>https://kubernetes.idsc.arch.cloud/1-setup/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://kubernetes.idsc.arch.cloud/1-setup/index.html</guid><description>The lab exercises require the installation and configuration of a few tools. This page will help you get started.
Local Installation The exercises assume a UNIX environment and are tested on macOS and on Windows with WSL 2 (Ubuntu).
macOS: the instructions use Homebrew. Run all commands in a terminal. Windows: install the Windows Subsystem for Linux as described below. Run all commands of this training inside the WSL terminal, not in PowerShell or the Command Prompt, unless stated otherwise. Requirements Administrator rights. On a company laptop, your IT department may have to install WSL and Docker Desktop for you At least 8 GB of RAM (16 GB recommended) and 20 GB of free disk space In a company network, access to Docker Hub, GitHub (github.com, ghcr.io), registry.k8s.io, mirror.gcr.io and PyPI. Ask your IT department to allow them in the proxy or firewall CPU architecture The Linux / WSL commands on this page download amd64 binaries. On a Windows machine with an ARM processor, replace amd64 with arm64.</description></item><item><title>2. Core Concepts</title><link>https://kubernetes.idsc.arch.cloud/2-core-concepts/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://kubernetes.idsc.arch.cloud/2-core-concepts/index.html</guid><description>This chapter covers the building blocks of Kubernetes, from the components of a cluster to running, exposing and configuring your applications.
What You Learn By the end of this chapter, you can:
name the components of a Kubernetes cluster and find them in your own cluster create and inspect resources with kubectl, both imperatively and with YAML manifests run applications as a Pod, Deployment, DaemonSet, StatefulSet, Job or CronJob make applications reachable with a Service, inside the cluster and from your machine configure applications with a ConfigMap and a Secret and store their data with a PersistentVolumeClaim find out why a workload doesn’t run and fix it make workloads robust with probes and resource limits, and scale them automatically Sections Section In the lab 2.1. Kubernetes Architecture Create your cluster and explore its components 2.2. kubectl and Manifests Work with contexts, the API and YAML manifests 2.3. Pods Run Pods with init and sidecar containers, labels and namespaces 2.4. Deployments Scale, update and roll back an application 2.5. Beyond Deployments Run DaemonSets, StatefulSets, Jobs and CronJobs 2.6. Services and Networking Reach apps via DNS, port forwarding and NodePort; blue/green 2.7. Configuration Configure an application with ConfigMaps and Secrets 2.8. Storage Keep data with volumes and PersistentVolumeClaims 2.9. Health and Resources Add probes, set requests and limits, autoscale under load 2.10. Troubleshooting Debug failing workloads with events, logs, top and exec How the Labs Work Each section starts with the theory in the presentation. The lab then puts it into practice. In 2.1, you create a local k3s cluster with k3d. You use this cluster for all labs. The cluster runs without an Ingress controller and without a load balancer. You reach your applications with port forwarding or a NodePort. Each lab ends with optional tasks. If you finish early, go ahead with them. The following labs don’t depend on them. Prerequisites All tools from 1. Setup must be installed and verified.</description></item><item><title>3. Fullstack App</title><link>https://kubernetes.idsc.arch.cloud/3-fullstack-app/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://kubernetes.idsc.arch.cloud/3-fullstack-app/index.html</guid><description>In this chapter, you build your own application and run it on Kubernetes, using everything you learned in chapter 2.
What You Build A small message board: you type a message in your browser, the application stores it, and the page lists all messages, the newest first. It consists of three containers:</description></item><item><title>4. Helm</title><link>https://kubernetes.idsc.arch.cloud/4-helm/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://kubernetes.idsc.arch.cloud/4-helm/index.html</guid><description>So far, you wrote every manifest yourself and applied it with kubectl. In this chapter, you use Helm, the package manager of Kubernetes: you install ready-made applications from charts and package your message board as a chart of its own.
What You Learn By the end of this chapter, you can:</description></item><item><title>5. Advanced Concepts</title><link>https://kubernetes.idsc.arch.cloud/5-advanced-concepts/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://kubernetes.idsc.arch.cloud/5-advanced-concepts/index.html</guid><description>Your message board runs on Kubernetes. In this chapter, you add what a production setup needs on top: friendly addresses, a database that operates itself, control over where Pods run and limits for what they may do.
What You Learn By the end of this chapter, you can:</description></item><item><title>6. Challenges</title><link>https://kubernetes.idsc.arch.cloud/6-challenges/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://kubernetes.idsc.arch.cloud/6-challenges/index.html</guid><description>These challenges take the message board further with what you learned in the labs. They are self-guided: there are no step-by-step instructions and no solutions. You decide how to solve each challenge, look things up in the labs and the documentation, and check the result yourself. A hint below each challenge tells you where to start.
Rating What to expect Easy Applies one lab to the message board Medium Combines several labs Hard Goes beyond the manifests, e.g. a change to the application image Starting point All challenges build on the releases from chapter 4: the message board messages in the namespace messages-dev and PostgreSQL postgresql in postgresql-dev. Challenge 1 also needs Traefik from 5.1, Challenge 2 the operator from 5.2. Change the chart in ~/labs/4.2/messages and roll out every change with helm upgrade.</description></item></channel></rss>