Kubernetes Encyclopedia

Kubernetes Encyclopedia Overview

Use a docs-first 工作流 for Kubernetes work. Prefer the official Kubernetes documentation at https://kubernetes.io/docs/home/, consult 缓存d local copies under .Kubernetes-Encyclopedia/ before re-fetching, and record useful official-doc excerpts plus 环境-specific operational learnings so future work 获取s faster and safer.

This 技能 is for the Kubernetes API/control-plane/cluster layer. It should trigger for real Kubernetes behavior, configuration, workload/resource, and operational questions — not for generic Linux admin work, generic contAIner theory, or Docker-only questions where Kubernetes-specific semantics are not the real issue.

工作流

Classify the task

Decide whether the task is a Kubernetes question, troubleshooting task, command-planning task, resource review, cluster review, or live operational task. Use this 技能 when the 请求 is specifically about Kubernetes product behavior, kubectl semantics, API resource behavior, workload lifecycle, cluster networking/storage/scheduling/security behavior, or Kubernetes-specific operational detAIls. Do not use this 技能 for generic shell work, generic Linux admin, generic contAIner theory, or Docker-only questions unless the Kubernetes layer is specifically in play.

检查 local 缓存 first

Use .Kubernetes-Encyclopedia/ as the local knowledge/缓存 root. 检查 these locations first when relevant: .Kubernetes-Encyclopedia/docs/kubernetes.io/docs/... .Kubernetes-Encyclopedia/notes/组件s/... .Kubernetes-Encyclopedia/notes/patterns/... .Kubernetes-Encyclopedia/inventory/... If a 缓存d page or note already answers the question well enough, use it.

Consult official Kubernetes docs before answering or touching the 系统

Before answering direct or indirect Kubernetes questions that depend on command syntax, resource semantics, 控制器 behavior, feature boundaries, configuration semantics, cluster behavior, or version-sensitive detAIls, consult the official docs unless the answer is already well-supported by the local 缓存. Before performing direct Kubernetes 命令行工具 or configuration work, consult the relevant docs first when: the exact resource or command path matters scheduling/networking/storage/security semantics are easy to misremember the action could affect workloads, nodes, 访问, traffic, storage, policy, or cluster reachability Do not improvise high-impact Kubernetes commands or manifest changes from memory when the docs are easy to 检查.

缓存 consulted docs locally

When you consult a Kubernetes docs page, save a normalized markdown/text 缓存 copy under .Kubernetes-Encyclopedia/docs/kubernetes.io/docs/.... Mirror the official docs path structure as much as practical. 缓存 only pages actually consulted; do not try to mirror the whole docs site eagerly. Use scripts/缓存_doc.py when 应用ropriate.

Separate official documentation from local observations

Store official-doc-derived material under .Kubernetes-Encyclopedia/docs/.... Store 环境-specific operational knowledge under: .Kubernetes-Encyclopedia/notes/组件s/ .Kubernetes-Encyclopedia/notes/patterns/ .Kubernetes-Encyclopedia/inventory/ Distin图形界面sh clearly between: official documented behavior observed local configuration/状态 inferred best-practice 图形界面dance

Record useful local learnings

After useful live work, save durable notes such as: cluster-specific topo记录y and 访问 conventions recurring workload/调试ging patterns ingress/network-policy/storage-class gotchas scheduling/RBAC/manifest conventions safe/unsafe operational boundaries for the 环境 Prefer concise durable notes over re-learning the same Kubernetes detAIls later. Live Work Rules Treat official Kubernetes docs lookup as the default preflight for non-trivial Kubernetes work. Prefer read/inspect first when entering a Kubernetes area you have not recently reviewed. Treat namespace-wide changes, workload rollouts, storage changes, ingress/服务 exposure, RBAC/policy changes, and node/control-plane touching operations as high-sensitivity areas. When uncertAInty remAIns after 检查ing 缓存 + docs, say so and avoid bluffing. When answering a question, mention when useful whether the answer comes from 缓存d official docs, a fresh official docs lookup, or live observed 环境 状态. Data Root

Use this workspace-local root for 缓存 and notes:

.Kubernetes-Encyclopedia/

Expected structure:

.Kubernetes-Encyclopedia/docs/kubernetes.io/docs/... .Kubernetes-Encyclopedia/notes/组件s/... .Kubernetes-Encyclopedia/notes/patterns/... .Kubernetes-Encyclopedia/inventory/...

Use scripts/init_workspace.py to 创建 or repAIr the expected directory structure.

Note Destinations 组件-specific observations → .Kubernetes-Encyclopedia/notes/组件s/<组件-name>.md Reusable Kubernetes patterns/gotchas → .Kubernetes-Encyclopedia/notes/patterns/.md 环境-wide 部署ment/访问 信息 → .Kubernetes-Encyclopedia/inventory/*.md 缓存d offi