SIG API Machinery Deep Dive - App...
summary
Server-side Apply reaches GA in 1.22 and controllers should use the new apply configurations package in client-go to avoid ghost-struct zero-value bugs (eg maxReplicas accidentally sent as 0); use the generated extract() to reconstruct owned fields and call apply forcefully to avoid optimistic concurrency loops. Priority and Fairness (APF) brings shuffle-sharding, queues and per-priority concurrency but exposes issues: kubelet probes needed an APF exemption, aggregated-server priority inversion workarounds, no cross-priority borrowing, cost estimation lands in 1.23, and watch retry appears in client-go 0.22.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:16Joe Betz
- 6:02Takeaways
- 15:55What is Priority Fairness
- 16:57RuleBased Flow Scheme API
- 19:19Cubelet Healthcheck
- 19:58Priority Inversion
- 21:38Priority Inversion Solution
- 23:47Server Concurrency Limit
- 24:57Priority Level
- 25:59Cost of Request
- 27:07Retry
related talks
35mIntro: SIG Apps
28mAdvanced API Machinery Topics: Aggregated API Servers and OpenAPI v3
21mApplication Runtime Platform Roundup: Galloping Go Bumps, Tracing Tales, and Readine...
31mSIG Architecture Intro And Deep Dive
19mHow to Future-proof your Go API
33mSIG Architecture Intro and Update
39mResilient REST APIs: The case for Parallel Change
52mEmbracing Complexity Entropy in Software Design