<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>5. Advanced Concepts :: Kubernetes Labs</title><link>https://kubernetes.idsc.arch.cloud/5-advanced-concepts/index.html</link><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><generator>Hugo</generator><language>en-us</language><atom:link href="https://kubernetes.idsc.arch.cloud/5-advanced-concepts/index.xml" rel="self" type="application/rss+xml"/><item><title>5.1. Ingress</title><link>https://kubernetes.idsc.arch.cloud/5-advanced-concepts/1-ingress/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://kubernetes.idsc.arch.cloud/5-advanced-concepts/1-ingress/index.html</guid><description>In this lab, you install the Ingress controller Traefik and make the message board from 4.2 reachable by a host name.
Step 1: Install Traefik Create the directories of this lab and change into it:
mkdir -p ~/labs/5.1/traefik cd ~/labs/5.1 Create the file values.yaml with the settings for Traefik in ~/labs/5.1/traefik, a directory of its own, because the Clean Up deletes all manifests in ~/labs/5.1 at once:</description></item><item><title>5.2. Operators</title><link>https://kubernetes.idsc.arch.cloud/5-advanced-concepts/2-operators/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://kubernetes.idsc.arch.cloud/5-advanced-concepts/2-operators/index.html</guid><description>In this lab, you install the operator CloudNativePG and let it run a replicated PostgreSQL cluster, including the failover when the primary goes down.
Step 1: Install the Operator Install the chart of CloudNativePG as the release cnpg into the new namespace cnpg-system:
helm install cnpg oci://ghcr.io/cloudnative-pg/charts/cloudnative-pg --version 0.29.1 \ -n cnpg-system --create-namespace Pulled: ghcr.io/cloudnative-pg/charts/cloudnative-pg:0.29.1 Digest: sha256:3245fa051bb21d0dd9246272f57a2760b4234817a164a3167d2a1e7fb9f63fd9 NAME: cnpg LAST DEPLOYED: Tue Oct 13 17:23:39 2026 NAMESPACE: cnpg-system STATUS: deployed REVISION: 1 DESCRIPTION: Install complete TEST SUITE: None NOTES: CloudNativePG operator should be installed in namespace "cnpg-system". ... Wait about 10 seconds and list the Pod of the operator:</description></item><item><title>5.3. Scheduling</title><link>https://kubernetes.idsc.arch.cloud/5-advanced-concepts/3-scheduling/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://kubernetes.idsc.arch.cloud/5-advanced-concepts/3-scheduling/index.html</guid><description>In this lab, you decide on which nodes your Pods run: you pin them to a node, spread them across all nodes and keep them off a node with a taint.
Step 1: Pin Pods to a Node Create the directory of this lab and change into it:
mkdir -p ~/labs/5.3 cd ~/labs/5.3 Label the node k3d-labs-agent-1 as a node with a fast disk:</description></item><item><title>5.4. Security</title><link>https://kubernetes.idsc.arch.cloud/5-advanced-concepts/4-security/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://kubernetes.idsc.arch.cloud/5-advanced-concepts/4-security/index.html</guid><description>In this lab, you restrict what a workload may do: which API calls it may make, what its container may do, which Pods a namespace admits and who may talk to a Pod.
Step 1: Grant a ServiceAccount Access With RBAC Create the directory of this lab and change into it:
mkdir -p ~/labs/5.4 cd ~/labs/5.4 Check whether the ServiceAccount reader, which doesn’t exist yet, may list Pods:</description></item></channel></rss>