7 — Aggregated APIs
Purpose
[stub: aggregated-apis]
Metadata
| Author | Amit Singh |
| Scope | kubernetes |
Local graph
Related notes
6 — Admission Webhooks
Why mutating webhooks always run before validating webhooks in the admission chain, so validation only ever sees the final, defaulted version of an object.
5 — API Server Internals
Why every request, regardless of which controller or kubectl call triggered it, passes through the same authn -> authz -> admission -> validation chain, making the API server the single enforcement point for cluster policy.
2 — Controller Manager
Why every built-in controller is level-triggered against the informer cache rather than edge-triggered off individual watch events, which is what makes reconciliation idempotent after a restart.
4 — etcd Internals
How etcd's MVCC revision counter, not object timestamps, is what makes watch resumption after a disconnect and optimistic concurrency via resourceVersion possible.