Target Picture from Day One
The map shows every building block of the shop. Before each chapter, it is clear which building block is being created now and what it is for.
Corporate Training · Kubernetes Fundamentals · 3 Days
In three days, your team learns to run applications on Kubernetes: from containers and the cluster architecture through deployments, services and configuration to rollouts, persistent data, Ingress and hardening. Along the way, participants work together to bring an online shop into the cluster – until it is reachable at its own address and survives a failure test.
Learning Objectives
After three days, participants do not just know the Kubernetes objects – they have configured, updated and secured a multi-part application themselves and brought it back into service after a failure.
Target Audience
The training is designed for teams that are introducing Kubernetes, running applications on it or will share responsibility for existing clusters in the future.
No prior knowledge of Kubernetes, YAML or programming is required.
The Hands-On Project
Monday morning, first day of the course: Clusterhausen Waffle Works – a fictional company, handmade since 1998 – is bringing its online shop to Kubernetes, and the participants are the new platform team. From this moment on, every exercise contributes to one goal. Three days later, the shop is configured, secured and reachable at its own address.
A “coming soon” page turns into a Deployment with multiple replicas, followed by Services, configuration and credentials, an order database with persistent storage and the path to the internet via Ingress. Along the way, the team rolls out new versions – including one that crashes on purpose. The shop stays online anyway, and the orders for the Pod Waffle survive every restart.
The map shows every building block of the shop. Before each chapter, it is clear which building block is being created now and what it is for.
Version 3 of the shop crashes on startup. The team sees how rolling updates and probes prevent an outage, and rolls back in a controlled way.
The first exercises provide close guidance; later, the sheets only define the goal and the acceptance criteria. Participants solve the finale largely on their own.
For every exercise, all manifests are available as a ready-made restore point. Anyone who gets stuck picks it up and is right back in.
Agenda
Day one lays the foundation, day two lets the application grow, and day three makes it production-ready. Every chapter leads into an exercise that adds a building block to the shop.
We adapt the order and depth to the group’s prior knowledge and pace. On request, we set priorities, such as extra time for Helm, security or examples from your environment.
Lab Environment
Every participant works in their own fully prepared environment with their own Kubernetes cluster. All course images are preloaded, so the exercises start without waiting.
Nobody shares a cluster. Everyone can delete, scale and provoke errors without disturbing anyone else.
The environment is conveniently accessible via the browser. No local installation is needed, and your IT department does not have to open anything up.
kubectl, an editor with YAML support and a terminal dashboard for the cluster are set up.
All exercises are run through completely in the lab environment beforehand, including the deliberately built-in failure scenarios.
After every exercise, all manifests are available as a restore point, so participants can rejoin at any time.
Materials
All chapters with our own diagrams, overview tables and manifest examples for easy reference.
Every exercise with a goal, prediction checks and tested manifests as the reference solution.
Short reviews on the course mornings reinforce what was covered the day before.
All manifests created during the course serve as templates for your own deployments.
One hour for your practical questions, two to four weeks after the course. Included in the price of every training.
Formats
The training takes place on your premises. Your team learns together and brings in questions about its own platform directly.
Live instruction with joint exercise phases and direct support in each participant’s own cluster – ideal for distributed teams.
We align focus areas and examples with your platform, such as security, Helm or running databases.
Your team already works with Kubernetes and wants to dive deeper into a specific topic – such as hardening, rollout strategies or troubleshooting in the cluster? Then a tailored workshop is the right fit.
After the course
The real work starts after the course. That is why every training includes an Ask the Trainer session: two to four weeks after the course, we meet online for one hour. Your participants send in the questions that came up while applying what they learned in your environment. That leaves the session free for what matters: specific answers for your systems, not the textbook case. The session is included in the price.
Pricing
3 days · €5,950 net for your team of up to 8 participants
includes materials, lab environment and Ask the Trainer session, plus travel and accommodation for on-site delivery
See the training overview for all terms.
Bundle offer
Both courses booked together: €9,950 net instead of €11,900, six days for the price of five. The courses run as two separate dates at least two weeks apart, both within six months, for the same team of up to 8 participants. Each course includes its own Ask the Trainer session, so the one from the container course falls right between the two dates.
Request bundleFAQ
Request
Briefly tell us the format and preferred time frame. We will get back to you with a proposed date and an individual quote. Your request is non-binding.
Your message has reached us. We will get back to you shortly with a proposed date and a quote for the Kubernetes training.
More Training
No container experience yet? Container training
The step before: the team moves the order shop from the server behind the bakery into containers and builds its own hardened images – the foundation for the cluster.
5 daysThe same company, one level down: the automation team builds the server landscape with Ansible – all the way to patch day across all systems.
3 daysThe growing business gets monitoring: tap into data sources, alert the right way and keep operations in view.
The teaching concept, the lab environment and the formats of all courses at a glance.