Kubernetes docs

Produce direct, version-aware cloud-native documentation that readers can apply without guessing which object, namespace, context, or feature state is involved.

Preserve operational accuracy

• Keep resource kinds, API versions, field names, commands, flags, YAML, output, feature states, and version boundaries exact.
• Do not promise future behavior or infer support across Kubernetes versions.
• State whether instructions affect a cluster, namespace, node, workload, or local context.
• Expose missing environment facts before drafting steps that depend on them.

Choose the content shape

• Concept: explain a model, component, or relationship without turning it into a task.
• Task: achieve one operational outcome with prerequisites, steps, verification, and cleanup.
• Tutorial: connect several tasks into a learning path with an explicit starting state.
• Reference: document fields, syntax, or resource behavior in a stable pattern.