Kubernetes for People Who Have to Run It

課程簡介

This is the highest level in the Library and it does not open by explaining what a container is for. It assumes you run something. Somebody else built the cluster, or you built it in a hurry two years ago, and you are now the person who gets rung when it stops. If you are still deciding whether to adopt this platform at all, read the fourth module of Securing a Cloud Estate You Didn't Build first — it works through a client who asked for a Kubernetes-scale answer to a spreadsheet-scale problem, and it gives you the words to refuse. That argument is finished and this segment does not reopen it. This one starts one step later. Everything here is taught from something that failed. You will apply an Ingress that is accepted and does nothing, schedule pods that never run, resolve a service name perfectly and connect to nothing, and fill a machine with 32 idle cores and 96 GB of untouched memory until it refuses the next twenty-six pods. That last one is the best technical moment in the source material: a node with headroom for around four hundred pods that can only be given 256 internal addresses per interface, so full-mesh communication caps density long before the processor does. The last module builds a control plane from nothing on a throwaway host. It fails four times first — a leftover file, forwarding disabled, a port already taken, and a bootstrap that hangs for four minutes and then gives up with an error that does not name the cause. The bring-up in the source notes stops at that hang, unfinished. This one finishes it. The thread running through all four modules is a single habit: in this platform a green tick means an object was accepted, and says nothing whatsoever about whether anything acted on it.

1. 01 What Is Actually Running, From the Outside In

   3 堂課程·1h 51m

   Everybody learns this platform inwards-out and then has to debug it outwards under pressure at 3am. This module builds the map in the direction an incident arrives from, and ends with the half of it…

2. 02 Where Things Land, and Why

   3 堂課程·1h 56m

   Anyone can place a pod once. The work is making the arrangement survive contact with eleven other engineers who have never heard of it, and that takes both halves of a mechanism most people only ever…

3. 03 The Network, and the Address Space That Ran Out

   3 堂課程·2h 41m

   Two labs in this module produce a cluster that is healthy by every measure your monitoring collects and cannot start another workload. The second one leaves no evidence at all after an hour, which is…

4. 04 The Bootstrap That Failed

   3 堂課程·2h 52m

   Most people reading this will never build a control plane, and that is a reasonable decision rather than a gap. Do it once anyway: the bring-up is the only occasion on which this platform enumerates…

常見問題

我將在 Kubernetes for People Who Have to Run It 中學到什麼？

For the engineer who already has this in production and did not choose it. The request path outside in, scheduling and node pools, the address space that runs out while the hardware sits idle, and a control-plane bootstrap worked through its real failure sequence to a conclusion.

我需要事先具備經驗嗎？

建議在開始 Kubernetes for People Who Have to Run It 前具備一些先備知識。

Kubernetes for People Who Have to Run It 需要多長時間？

Kubernetes for People Who Have to Run It 包含 4 個單元和 12 堂課程。你可以按自己的進度學習。

我如何取得存取權限？

Kubernetes for People Who Have to Run It 包含在任何付費訂閱方案中。