← Kubernetes Patterns, Second Edition

Learn / Kubernetes Patterns, Second Edition

06 - Automated Placement

Foundational Patterns: advanced mastery of Automated Placement, including every named section across book pages 61-75.

Learning path

0%

0 of 4 sections marked complete · about 39 minutes

Learning objectives

What you will be able to explain

  • Recognize the recurring problem
  • Choose the Kubernetes-native solution
  • Audit the pattern invariants
  • Match the pattern vocabulary
  • Evaluate forces and tradeoffs
  • Apply the pattern to a concrete workload

Section 01

Recognize the recurring problem to Audit the pattern invariants

01

Recognize the recurring problem

The pattern begins with this recurring cloud native force: Workloads need placement that satisfies resources, hardware, co-location, separation, topology balance, and node exclusions without manual node assignment.

Guided checkpoint

Which statement best captures the force that motivates this pattern?

Source: Chapter 6, Problem, book pages 61-75

02

Choose the Kubernetes-native solution

The solution maps the problem to Kubernetes primitives: Let the scheduler filter and score nodes using requests, scheduler profiles, affinity, anti-affinity, topology spread, taints, and tolerations.

Guided checkpoint

Which mechanism best expresses the pattern?

Source: Chapter 6, Solution, book pages 61-75

03

Audit the pattern invariants

All listed invariants belong to the Automated Placement solution and must be understood together.

Guided checkpoint

Mark each statement as a sound part of the pattern.

Source: Chapter 6, Solution, book pages 61-75

Section 02

Match the pattern vocabulary to Apply the pattern to a concrete workload

01

Match the pattern vocabulary

These concepts form the implementation vocabulary of Automated Placement.

Guided checkpoint

Match each role or mechanism to the Kubernetes concept used by this pattern.

Source: Chapter 6, Solution, book pages 61-75

02

Evaluate forces and tradeoffs

The Discussion section weighs these benefits, costs, and failure modes rather than presenting the pattern as universally free.

Guided checkpoint

Judge the operational claims, including deliberately unsafe shortcuts.

Source: Chapter 6, Discussion, book pages 61-75

03

Apply the pattern to a concrete workload

Required node affinity filters eligible nodes by label.

Guided checkpoint

GPU workloads must run only on labeled GPU nodes. Which mechanism expresses the hard requirement?

Source: Chapter 6, Solution, book pages 61-75

Section 03

Choose among competing Kubernetes mechanisms to Know when the pattern is the wrong tool

01

Choose among competing Kubernetes mechanisms

Soft spread expresses balance preference without blocking all placement.

Guided checkpoint

Three replicas should be balanced across zones but still schedule if perfect balance is impossible. What fits?

Source: Chapter 6, Solution, book pages 61-75

02

Operational practice audit

Production use requires these lifecycle, reliability, and observability judgments.

Guided checkpoint

Decide which production practices are sound.

Source: Chapter 6, Discussion, book pages 61-75

03

Know when the pattern is the wrong tool

Tolerations permit; selection needs additional constraints.

Guided checkpoint

What does a toleration mean by itself?

Source: Chapter 6, Discussion, book pages 61-75

Section 04

Synthesize the complete pattern

01

Synthesize the complete pattern

Balanced placement combines feasibility, resilience, and scheduler flexibility.

Guided checkpoint

How should a resilient three-zone service express placement?

Source: Chapter 6, Problem, Solution, and Discussion, book pages 61-75

Knowledge check

Turn understanding into recall.

The quiz now follows the same concepts in scored form. You can return to this lesson from the quiz whenever a gap appears.

Start the quiz →Back to course