# watch Published articles for watch. 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】Watch 路径（服务端）：长连接、410 Gone 与 timeout DevFeed: [【kube-apiserver】Watch 路径（服务端）：长连接、410 Gone 与 timeout]() Original publisher: [Read original article]() Author: Liao Tonglang Published: 2026-08-28T00:00:00Z Content type: article Language: zh Sources: [土法炼钢 - 系统与基础设施]() Topics: [Kubernetes](), [HTTP](), [kubectl]() Tags: [410-gone](), [apiserver](), [bookmark](), [cacher](), [distributed](), [etcd](), [etcd3](), [informer](), [kubernetes](), [resourceversion](), [rest](), [timeout](), [v1-30-3](), [watch]() ### AI overview This article explains the Kubernetes v1.30.3 apiserver Watch path, from the REST handler through cacher and etcd3 watchers. It distinguishes 410 Gone caused by cacher ring-buffer eviction from errors propagated from etcd compaction, and covers resourceVersion semantics, timeouts, bookmarks, connection lifecycle, and the boundary with client-go Informer. ### Source excerpt 钉 Kubernetes v1.30.3 服务端 Watch 路径：从 REST handler 到 cacher/etcd3 watcher 的建立过程、resourceVersion=0 与具体 RV 的语义差异、410 Gone 与 etcd ErrCompacted 的映射、bookmark 推送与连接生命周期，以及与 client-go Informer 的边界。 ## 【kube-apiserver】resourceVersion 与 Revision 映射：mod revision、continue 与一致性读期望 DevFeed: [【kube-apiserver】resourceVersion 与 Revision 映射：mod revision、continue 与一致性读期望]() Original publisher: [Read original article]() Author: Liao Tonglang Published: 2026-08-28T00:00:00Z Content type: tutorial Language: zh Sources: [土法炼钢 - 系统与基础设施]() Topics: [Kubernetes](), [API](), [Caching]() Tags: [410-gone](), [api](), [apiserver](), [cache](), [consistency](), [continue-token](), [distributed](), [etcd](), [kubernetes](), [pagination](), [resourceversion](), [revision](), [v1-30-3](), [watch]() ### AI overview This article explains how Kubernetes resourceVersion maps to etcd mod_revision, including the different semantics for individual objects and List responses. It covers Watch starting points, continue-token pagination and its costs, compaction-related 410 Gone errors, and consistency differences between watch-cache and etcd read paths. The discussion is anchored to Kubernetes v1.30.3 and etcd v3.5.33. ### Source excerpt 钉 Kubernetes resourceVersion 字段与 etcd mod revision 的对应关系；分析 continue token 的分页语义与成本；说明不同 List 路径的一致性期望差异；以及 410 Gone 与 ErrCompacted 的分列。版本锚定 Kubernetes v1.30.3 / etcd v3.5.33。 ## 【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 轴。 ## 【etcd】MVCC 数据模型：Revision、keyIndex 与 generation DevFeed: [【etcd】MVCC 数据模型：Revision、keyIndex 与 generation]() Original publisher: [Read original article]() Author: Liao Tonglang Published: 2026-08-26T00:00:00Z Content type: tutorial Language: zh Sources: [土法炼钢 - 系统与基础设施]() Topics: [etcd](), [Raft](), [Kubernetes]() Tags: [compaction](), [distributed](), [etcd](), [generation](), [keyindex](), [kubernetes](), [mvcc](), [raft](), [revision](), [treeindex](), [v3](), [v3-5](), [v3-5-33](), [watch]() ### AI overview This article analyzes etcd v3.5.33's MVCC data model through three concepts: globally ordered revisions, keyIndex generations that track key lifecycles, and the division of responsibilities between the in-memory treeIndex and the bbolt backend. It explains how these structures support historical Watch replay, transaction comparisons, compaction, and Kubernetes resourceVersion semantics, while distinguishing etcd revisions from Raft indexes. ### Source excerpt 拆解 etcd v3.5.33 的 Revision (main, sub) 全序、keyIndex/generation 生命周期与 treeIndex 分工；简要对照 v2 平面键空间，交代 MVCC 与 Watch/compaction 的语义基础。 ## 【etcd】生产全景：缺口、五轴坐标系与 16 篇路线 DevFeed: [【etcd】生产全景：缺口、五轴坐标系与 16 篇路线]() Original publisher: [Read original article]() Author: Liao Tonglang Published: 2026-08-26T00:00:00Z Content type: article Language: zh Sources: [土法炼钢 - 系统与基础设施]() Topics: [etcd](), [Kubernetes]() Tags: [control-plane](), [distributed](), [etcd](), [kubernetes](), [lease](), [mvcc](), [overview](), [raft](), [v3-5](), [v3-5-33](), [wal](), [watch]() ### AI overview This article positions an etcd production series by identifying gaps in existing coverage and defining five troubleshooting axes spanning Raft consensus, WAL persistence and recovery, MVCC storage and capacity, Watch behavior, and Lease handling. It anchors the series to etcd v3.5.33 and points to Kubernetes control-plane coupling and a 16-article reading route. ### Source excerpt 相对 distributed/50、39、13 钉清 etcd 生产内核缺口；定义 Raft/WAL/MVCC/Watch/Lease 五轴排障坐标系，给出 16 篇阅读路线与 K8s 控制面耦合指针。版本锚定 v3.5.33。 ## 【etcd】Lease 与 KeepAlive：TTL、checkpoint 与 Leader 切换 DevFeed: [【etcd】Lease 与 KeepAlive：TTL、checkpoint 与 Leader 切换]() Original publisher: [Read original article]() Author: Liao Tonglang Published: 2026-08-26T00:00:00Z Content type: tutorial Language: zh Sources: [土法炼钢 - 系统与基础设施]() Topics: [etcd](), [Raft](), [Kubernetes](), [Remote Procedure Call (RPC)]() Tags: [api](), [checkpoint](), [client](), [concurrency](), [distributed](), [etcd](), [follower](), [k8s](), [keepalive](), [kubernetes](), [lease](), [lessor](), [primary](), [raft](), [ttl](), [v3](), [v3-5-33](), [watch]() ### AI overview This article explains etcd v3.5.33 lease behavior, focusing on the lessor's primary, demote, and promote roles, the KeepAlive renewal path that normally bypasses Raft, lease checkpointing, and TTL changes during leader transitions. It also discusses implications for Kubernetes Node Leases and distributed locks. ### Source excerpt 钉 etcd v3.5.33 lessor 的 primary/demote/promote、KeepAlive 不经 Raft 的 Renew 路径、LeaseCheckpoint 与 Promote 时 TTL 展期，以及 Leader 切换对 Node Lease 的排障落格。 ## 【etcd】Watch 机制：watchableStore、synced/unsynced 与 ErrCompacted DevFeed: [【etcd】Watch 机制：watchableStore、synced/unsynced 与 ErrCompacted]() Original publisher: [Read original article]() Author: Liao Tonglang Published: 2026-08-26T00:00:00Z Content type: tutorial Language: zh Sources: [土法炼钢 - 系统与基础设施]() Topics: [etcd](), [Raft](), [Remote Procedure Call (RPC)](), [Kubernetes]() Tags: [apiserver](), [apply](), [compaction](), [distributed](), [errcompacted](), [etcd](), [io](), [k8s](), [kubernetes](), [lag](), [leader](), [lease](), [mvcc](), [notify](), [raft](), [range](), [restore](), [revision](), [rpc](), [v3-5](), [v3-5-33](), [watch](), [watchablestore]() ### AI overview This article examines the etcd v3.5.33 watchableStore implementation, including synced and unsynced watcher groups, victims caused by backpressure, Apply-time notification, historical synchronization, and the ErrCompacted client resynchronization boundary. It also discusses event ordering, follower watch progress, and interactions with Kubernetes apiserver watch caches. ### Source excerpt 钉 etcd v3.5.33 watchableStore 的 synced/unsynced/victims 三分法、Apply 后 notify 与历史追赶 syncWatchersLoop，以及 CompactRevision 触发 ErrCompacted 时的客户端重同步边界。 ## 【etcd】treeIndex 与 Apply 管道：propose -\> commit -\> apply DevFeed: [【etcd】treeIndex 与 Apply 管道：propose -\> commit -\> apply]() Original publisher: [Read original article]() Author: Liao Tonglang Published: 2026-08-26T00:00:00Z Content type: tutorial Language: zh Sources: [土法炼钢 - 系统与基础设施]() Topics: [etcd](), [Raft](), [Back end]() Tags: [applied-index](), [apply](), [backend](), [bbolt](), [commit](), [compaction](), [distributed](), [etcd](), [index](), [kubernetes](), [mvcc](), [raft](), [range](), [recovery](), [revision](), [store](), [treeindex](), [txn](), [v3-5](), [wal](), [watch]() ### AI overview This tutorial explains the etcd v3.5.33 apply pipeline from Raft commit to MVCC application. It covers the separation between propose, commit, and apply; the roles of treeIndex and bbolt; consistent-index updates; watch notification timing; and troubleshooting committed-versus-applied lag. ### Source excerpt 走读 etcd v3.5.33 从 Raft commit 到 MVCC apply 的串行管道：treeIndex 与 bbolt 分工、consistent index、watchableStore 通知触发点，以及 committed/applied 分列排障。 ## 【etcd】单 Raft 组与服务器角色：Leader、Follower、Learner 与 request 路由 DevFeed: [【etcd】单 Raft 组与服务器角色：Leader、Follower、Learner 与 request 路由]() Original publisher: [Read original article]() Author: Liao Tonglang Published: 2026-08-26T00:00:00Z Content type: article Language: zh Sources: [土法炼钢 - 系统与基础设施]() Topics: [etcd](), [Raft](), [gRPC]() Tags: [apiserver](), [apply](), [atomic](), [commit](), [compaction](), [distributed](), [etcd](), [etcdserver](), [follower](), [kubernetes](), [leader](), [learner](), [linearizable](), [raft](), [request](), [single-raft-group](), [v3](), [v3-5](), [v3-5-33](), [wal](), [watch]() ### AI overview This article explains how etcd v3.5.33 embeds a single Raft group, separates EtcdServer responsibilities from the Raft library, and routes requests across Leader, Follower, and Learner roles. It covers gRPC write forwarding, linearizable and serializable reads, and the handling of watch, lease, and mutating requests. ### Source excerpt 钉清 etcd v3.5.33 单 Raft 组拓扑、EtcdServer 与 go.etcd.io/raft/v3 边界、Leader/Follower/Learner 角色及 gRPC 写读路由；与 distributed/13 分工。 ## 【etcd】排障五轴：Raft/WAL/MVCC/Watch/Lease 口令表 DevFeed: [【etcd】排障五轴：Raft/WAL/MVCC/Watch/Lease 口令表]() Original publisher: [Read original article]() Author: Liao Tonglang Published: 2026-08-26T00:00:00Z Content type: tutorial Language: zh Sources: [土法炼钢 - 系统与基础设施]() Topics: [etcd](), [Kubernetes]() Tags: [apiserver](), [applied-index](), [apply](), [committed-index](), [compaction](), [distributed](), [errcompacted](), [etcd](), [five-axes](), [incident](), [keepalive](), [kubernetes](), [lag](), [lease](), [mvcc](), [node-lease](), [raft](), [restore](), [troubleshooting](), [ttl](), [v3](), [v3-5](), [v3-5-33](), [wal](), [watch]() ### AI overview This troubleshooting article organizes etcd failures into five diagnostic axes: Raft consensus, WAL persistence and recovery, MVCC storage and capacity, Watch client synchronization, and Lease TTL semantics. It maps symptoms to axes, explains relevant etcdctl health and status fields, and notes Kubernetes control-plane relationships, including apiserver and Node Lease behavior. The article is anchored to etcd v3.5.33. ### Source excerpt 按 Raft、WAL、MVCC、Watch、Lease 五轴做症状否证；解释 etcdctl endpoint status/health 字段语义；并对照 K8s 控制面 apiserver 超时与 Node Lease 漂移。 ## 【etcd】Kubernetes 控制面耦合：apiserver、resourceVersion 与 Node Lease DevFeed: [【etcd】Kubernetes 控制面耦合：apiserver、resourceVersion 与 Node Lease]() Original publisher: [Read original article]() Author: Liao Tonglang Published: 2026-08-26T00:00:00Z Content type: tutorial Language: zh Sources: [土法炼钢 - 系统与基础设施]() Topics: [etcd](), [Kubernetes](), [API](), [Cache]() Tags: [api](), [apiserver](), [cache](), [control-plane](), [distributed](), [etcd](), [kubernetes](), [lease](), [mvcc](), [node-lease](), [raft](), [resourceversion](), [v3-5-33](), [watch](), [watch-cache]() ### AI overview This article explains how Kubernetes control-plane components interact with etcd. It covers the kube-apiserver boundary, the mapping of resourceVersion to etcd mod revision, Node Lease storage, watch cache behavior, and how compaction, caching, and event sharding affect troubleshooting and etcd load. ### Source excerpt 钉 kube-apiserver 与 etcd 的分层边界；resourceVersion 如何映射 Revision MVCC；Node Lease 如何落在 Lease 轴；以及 apiserver 超时应如何分列到 Raft/Watch/Quota 五轴。 ## 【etcd】Compaction、Defrag 与容量：quota、alarm 与 SLO DevFeed: [【etcd】Compaction、Defrag 与容量：quota、alarm 与 SLO]() Original publisher: [Read original article]() Author: Liao Tonglang Published: 2026-08-26T00:00:00Z Content type: tutorial Language: zh Sources: [土法炼钢 - 系统与基础设施]() Topics: [etcd](), [Raft](), [Kubernetes]() Tags: [alarm](), [bbolt](), [benchmark](), [compaction](), [defrag](), [distributed](), [errcompacted](), [etcd](), [follower](), [kubernetes](), [lag](), [leader](), [mvcc](), [nospace](), [performance](), [quota](), [raft](), [resourceversion](), [v3](), [v3-5](), [v3-5-33](), [watch]() ### AI overview This technical article explains how etcd v3.5.33 compaction, defragmentation, quota handling, and the NOSPACE alarm interact. It distinguishes revision-history removal from bbolt file reclamation, describes periodic and revision-based auto-compaction, and connects retention, quota, defrag pauses, and Watch or Kubernetes control-plane behavior to operational SLOs. ### Source excerpt 钉 etcd v3.5.33 MVCC compaction 与 bbolt defrag 的分工、auto-compaction 保留窗口、quota-backend-bytes 与 NOSPACE alarm 写入门，以及 ErrCompacted 如何写进 Watch SLO。 ## 【分布式系统百科】etcd 深度解剖：从 Watch 机制到 MVCC 存储引擎 DevFeed: [【分布式系统百科】etcd 深度解剖：从 Watch 机制到 MVCC 存储引擎]() Original publisher: [Read original article]() Author: Liao Tonglang Published: 2026-04-13T00:00:00Z Content type: article Language: zh Sources: [土法炼钢 - 系统与基础设施]() Topics: [etcd](), [Kubernetes](), [Raft]() Tags: [apiserver](), [boltdb](), [compaction](), [distributed](), [distributed-coordination](), [distributed-systems](), [etcd](), [kubernetes](), [lease](), [mvcc](), [raft](), [revision](), [streaming](), [watch]() ### AI overview This article explains etcd's persistent Watch mechanism, revision-based event replay, MVCC storage, and its relationship with Raft and WAL. It also describes how Kubernetes components use etcd Watch events to propagate Deployment and Pod changes, and discusses compaction limits and recovery through full resynchronization. ### Source excerpt 深入剖析 etcd 的核心机制：持久化 Watch 与 Revision 追溯、Lease 租约机制、基于 BoltDB 的 MVCC 存储引擎、与 Raft 共识的联动方式，以及在 Kubernetes 中的关键角色。涵盖性能调优策略、容量限制与规模化方案。 ## 【分布式系统百科】分布式 KV 存储对比：etcd、TiKV 与 FoundationDB DevFeed: [【分布式系统百科】分布式 KV 存储对比：etcd、TiKV 与 FoundationDB]() Original publisher: [Read original article]() Author: Liao Tonglang Published: 2026-04-13T00:00:00Z Content type: comparison Language: zh Sources: [土法炼钢 - 系统与基础设施]() Topics: [etcd](), [Raft](), [Kubernetes]() Tags: [bbolt](), [boltdb](), [compaction](), [coreos](), [distributed](), [distributed-systems](), [errcompacted](), [etcd](), [go](), [k8s](), [kubernetes](), [lease](), [mmap](), [mvcc](), [raft](), [readindex](), [revision](), [single-raft-group](), [ssd](), [v3](), [wal](), [watch]() ### AI overview This Chinese-language comparison examines etcd, TiKV, and FoundationDB as distributed key-value stores for metadata. It focuses on architecture, implementation, performance, and limitations, with detailed coverage of etcd's single Raft group, MVCC, Watch, Lease, bbolt storage engine, linearizable reads, compaction, and defragmentation. ### Source excerpt 一个典型的架构评审场景：团队需要一个分布式键值存储来承载新系统的元数据。候选方案三个----etcd、TiKV、FoundationDB。三者都提供强一致性保证，都经过大规模生产验证，但设计目标截然不同。选错了，轻则性能不达标，重则数据丢失后无法恢复。这篇文章从架构、实现、性能和局限四个维度，把三个系统拆开来看。 ## The WET Codebase DevFeed: [The WET Codebase]() Original publisher: [Read original article]() Published: 2020-07-13T00:00:00Z Content type: opinion Language: en Sources: [Dan Abramov]() Topics: [Code](), [Software]() Tags: [code](), [software](), [talk](), [watch]() ### AI overview A conference talk argues that strict adherence to eliminating code duplication can produce software that is difficult to understand. The article shares the talk, including its transcript, as a starting point for team discussion. ### Source excerpt Come waste your time with me. ## Watch: Ember at 10 feet DevFeed: [Watch: Ember at 10 feet]() Original publisher: [Read original article]() Published: 2014-12-22T00:00:00Z Content type: article Language: en Sources: [Robin Ward]() Topics: [Ember]() Tags: [ember](), [video](), [watch]() ### AI overview A video of the author's "Ember at 10 feet" talk from the Embergarten Saturday Symposium is available to watch. The post also links to source code and an online demo. ### Source excerpt Previously I posted notes and links for my talk about "Ember at 10 feet" from the Embergarten Saturday Symposium. Today my awesome friends at Unspace posted a video of the talk, which you can watch below: Source Code | Online Demo