Skill · Kubernetes · Understand, install and maintain a cluster
Control where Pods are placed
Decide where Pods run: nodeSelector, affinity and anti-affinity, taints and tolerations, and spreading across zones with topologySpreadConstraints.
Start lesson 1The Kubernetes domain
- 2 lessons
- ~2 h 20 of reading
- 2 quizzes
- 0 proof lab
The path
Where it comes from, where it leads
What you need to know first, where you stand on this skill, and what it opens next. Your status is computed in your browser, from what you have read and passed.
Before · 1 prerequisite
Recommended before · 1
This skill, for you
Control where Pods are placed
Computing
It unlocks · nothing yet
No other skill requires it: it is an end-of-path skill.
The path through the foundations From the most upstream foundation to this skill: what is in place, what remains to read.
Lessons
How to learn it
2 lessons, about ~2 h 20, in program order. Each lesson ends with its quiz.
The program
2 lessons · ~2 h 20
- 1Assigner des nodes aux Pods (in French)· 95 min
- 2Scheduling avancé (in French)· 45 min
Beyond the lessons
Assess, practise, pass the proof
Reading a lesson confirms nothing. A skill is confirmed by a passed quiz, practised in a guided lab, and put to the test by a challenge or a mission; an imported lab result is not verified by the site.
Assess yourself
2 quizzes
At the end of the lessons: passed at 70%, they confirm the skill.
Practice
2 guided labs
Proof
No proof
A practical proof is a challenge, a capstone or a declared lab.
Used by the mission “Bring an application back on a cluster”, which has its proof.
Placement test
Preparing the questions…
Your answers in detail
For each question asked: your answer, the correct answer, its explanation and the page to reread.
Around it
Who requires it, who teaches it
Required by
In red: the certification it prepares for.
Taught by
Same block · Understand, install and maintain a cluster
- Explain the architecture of a Kubernetes cluster
- Install a Kubernetes cluster
- Make the control plane of a kubeadm cluster highly available
- Cap a namespace's resources
- Maintain and manage nodes without service interruption
- Back up and restore a cluster's state
- Detect and migrate deprecated APIs before an upgrade
- Upgrade a kubeadm cluster by one minor version
- Use custom resources and operators