# apf Published articles for apf. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## kube-apiserver / Kubernetes 控制面内核：storage、cacher、Admission 与 APF DevFeed: [kube-apiserver / Kubernetes 控制面内核：storage、cacher、Admission 与 APF]() Original publisher: [Read original article]() Author: Liao Tonglang Published: 2026-08-28T00:00:00Z Content type: article Language: zh Sources: [土法炼钢 - 系统与基础设施]() Topics: [Kubernetes](), [etcd](), [Caching](), [API](), [site-reliability-engineering](), [Authentication](), [Authorization](), [rbac]() Tags: [admission](), [apf](), [apiserver](), [authentication](), [authorization](), [cacher](), [control-plane](), [distributed](), [etcd](), [kubernetes](), [oidc](), [pagination](), [plan](), [rbac](), [resourceversion](), [storage](), [v1-30-3](), [watch](), [watch-cache](), [webhook]() ### AI overview This article introduces a 16-part series on the kube-apiserver production request path, covering storage.Interface and etcd3, resourceVersion, watch cache behavior, List and Watch operations, Admission and Webhooks, authentication, authorization, auditing, APF, and extension boundaries. It explains how to distinguish failures across these layers and when to investigate kube-apiserver instead of directly querying etcd. The discussion is anchored to Kubernetes v1.30.3 and etcd v3.5.33, with experiments explicitly noted as not yet run. ### Source excerpt 补齐 etcd 系列 K8s 耦合篇之上的 kube-apiserver 生产内核：storage.Interface、watch cache、resourceVersion、Admission/Webhook、APF，并以排障与相对 etcd 的分层收束。 ## 【kube-apiserver】控制面全景：缺口、五轴坐标系与 16 篇路线 DevFeed: [【kube-apiserver】控制面全景：缺口、五轴坐标系与 16 篇路线]() Original publisher: [Read original article]() Author: Liao Tonglang Published: 2026-08-28T00:00:00Z Content type: tutorial Language: zh Sources: [土法炼钢 - 系统与基础设施]() Topics: [Kubernetes](), [etcd]() Tags: [admission](), [apf](), [apiserver](), [auth](), [control-plane](), [distributed](), [etcd](), [kubernetes](), [network](), [overview](), [storage](), [v1-30-3](), [watch](), [watch-cache]() ### AI overview This article maps gaps in existing coverage of the Kubernetes control plane and proposes a 16-part reading route organized around Storage, Watch, Admission, Auth, and APF. It anchors the discussion to Kubernetes v1.30.3 and etcd v3.5.33, focusing on how requests travel through kube-apiserver and how to distinguish admission, caching, backend, and timeout failures. ### Source excerpt 相对 etcd/13、distributed/50、k8s-network 补齐 kube-apiserver 生产内核缺口；以 Storage/Watch/Admission/Auth/APF 五轴为坐标系定义 16 篇阅读路线；版本锚定 Kubernetes v1.30.3。 ## 【kube-apiserver】进程与请求路径：generic apiserver、HandlerChain 与 REST 路由 DevFeed: [【kube-apiserver】进程与请求路径：generic apiserver、HandlerChain 与 REST 路由]() Original publisher: [Read original article]() Author: Liao Tonglang Published: 2026-08-28T00:00:00Z Content type: tutorial Language: zh Sources: [土法炼钢 - 系统与基础设施]() Topics: [Kubernetes](), [API]() Tags: [admission](), [apf](), [apiserver](), [audit](), [authn](), [authz](), [distributed](), [generic-apiserver](), [gvr](), [handlerchain](), [kubernetes](), [request-path](), [rest](), [v1-30-3]() ### AI overview This tutorial explains the Kubernetes v1.30.3 kube-apiserver process model, the generic apiserver framework, HandlerChain ordering, GVR routing, and the points where requests can be rejected before reaching storage. It also distinguishes failures caused by APF, authentication and authorization, admission, and storage. ### Source excerpt 拆解 kube-apiserver 进程模型与 generic apiserver 框架；钉 HandlerChain 各插槽顺序与失败落点；说明 GVR 路由机制与请求在到达 storage 前可能被拦截的位置。版本锚定 Kubernetes v1.30.3。 ## 【kube-apiserver】排障五轴：Storage、Watch、Admission、Auth、APF DevFeed: [【kube-apiserver】排障五轴：Storage、Watch、Admission、Auth、APF]() Original publisher: [Read original article]() Author: Liao Tonglang Published: 2026-08-28T00:00:00Z Content type: tutorial Language: zh Sources: [土法炼钢 - 系统与基础设施]() Topics: [Kubernetes](), [API](), [etcd]() Tags: [admission](), [apf](), [apiserver](), [auth](), [authz](), [distributed](), [etcd](), [five-axes](), [kubernetes](), [metrics](), [storage](), [troubleshooting](), [v1-30-3](), [watch]() ### AI overview A troubleshooting guide for kube-apiserver organized around five diagnostic axes: Storage, Watch, Admission, Auth, and API Priority and Fairness. It maps symptoms such as 504, 410 Gone, 401, 403, webhook timeouts, list storms, and OOM to likely axes, explains when to investigate etcd, and emphasizes that commands and metrics were not executed in the author's environment. ### Source excerpt 按 Storage/Watch/Admission/Auth/APF 五轴做症状否证；给出完整五轴命令表与症状->轴映射（504、410、401、403、webhook 超时、List 风暴、OOM）；说明 apiserver_request_duration_seconds 等核心 metrics 语义；并提供决策树：何时穿透到 etcd/15，何时留在 apiserver 轴。 ## 【kube-apiserver】APF 与 max-in-flight：公平排队、504 与 etcd lag 分列 DevFeed: [【kube-apiserver】APF 与 max-in-flight：公平排队、504 与 etcd lag 分列]() Original publisher: [Read original article]() Author: Liao Tonglang Published: 2026-08-28T00:00:00Z Content type: article Language: zh Sources: [土法炼钢 - 系统与基础设施]() Topics: [Kubernetes](), [API](), [SRE](), [Linux]() Tags: [apf](), [api](), [apiserver](), [distributed](), [etcd](), [fairness](), [fairqueuing](), [flowcontrol](), [k8s](), [kubernetes](), [lag](), [max-in-flight](), [priority](), [timeout](), [v1-30-3]() ### AI overview This article explains how Kubernetes v1.30.3 protects kube-apiserver from overload through API Priority and Fairness (APF) and the older max-in-flight limits. It distinguishes 429 responses, APF queue timeouts that can produce 504 responses before storage is reached, etcd latency, and admission webhook delays, and describes APF's FlowSchema, PriorityLevelConfiguration, fair queuing, and shuffle sharding mechanisms. ### Source excerpt 钉 K8s v1.30.3 的 API Priority and Fairness（APF）：FlowSchema 匹配、PriorityLevelConfiguration 公平排队（SFVR）、与旧 max-in-flight flag 的共存关系；429/timeout/504 在 APF 排队、etcd_request_duration_seconds、Admission Webhook 三轴的分列；pkg/util/flowcontrol 路径；APF 与简单 max-in-flight 的运维复杂度争论。