Inspect before downloading
See what is inside
These previews come from the published bundle files, so you can judge the method and writing before using it.
Tool guide
Kubernetes
Defines source-aware container orchestration and cluster operations, evidence handling, and action boundaries.
Read the fileOverview
Kubernetes overview
Use this bundle to structure container orchestration and cluster operations while keeping official-source context separate from account, organization, project, document, or environment.
Read the fileWorkflow
Kubernetes source-aware triage
1. State the requested decision or deliverable. 2. Inventory evidence: cluster version and context, namespaces and ownership, manifests and applied objects, workloads, services, ingress.
Read the fileTemplate
Kubernetes operations and change brief
Review-ready brief for container orchestration and cluster operations, evidence quality, verification, and controlled next actions.
Read the fileIs this bundle right for your task?
Who it is for
- Platform engineers, Kubernetes operators, DevOps and SRE teams, application owners, and reviewers planning cluster changes or investigations
When to use it
- A workload, service, ingress, storage, configuration, or access issue needs cluster evidence reconciled before a diagnosis is stated.
- A rollout or incident review needs manifests, applied objects, status, events, logs, metrics, history, ownership, and version context compared.
- A Kubernetes change needs a reviewable recommendation with alternatives, validation checks, backups, rollback steps, stop conditions, and approval gates.
What you need to provide
- Cluster version and context, namespaces and owners, desired manifests, applied objects, workloads, services, ingress, storage, configuration, RBAC, and service-account evidence.
- Relevant status, events, logs, metrics, rollout history, image details, policies, backups, proposed change, validation and rollback plan, access scope, and approvals.
Tasks and expected outputs
Questions it helps answer
- Prepare a kubernetes operations and change brief without fabricating local facts.
- Separate verified, provided, assumed, and missing evidence.
- Produce review-ready decisions with explicit verification and approval boundaries.
What it helps produce
- Kubernetes operations and change brief
Practical example
Use it with an agent
Load the bundle as context, provide the evidence named above, then adapt this example to your situation.
Load the Kubernetes bundle and provide the cluster version and context, namespace, manifests and applied-object output, workload and service status, events, relevant logs and metrics, rollout history, RBAC evidence, policy constraints, backup state, and proposed rollback. Ask the agent to separate known state from hypotheses and draft a Kubernetes operations and change brief with verification commands and approval boundaries, without applying anything.
Context path: bundles/tools/kubernetes
What the bundle includes
Tools
- Kubernetes
Frameworks
- source-evidence matrix
- container-orchestration-and-cluster-operations evidence matrix
- qualified-review gate
Evaluations
- Kubernetes source-awareness check
Sources used to build this bundle
These are the public references behind the role definition and operating guidance. The bundle does not replace current documentation or evidence from your site.
Limitations and safe use
Do not use this for
- Inventing cluster state, resources, images, secrets, permissions, health, or capacity; applying or deleting resources or changing images, configuration, secrets, access, scaling, networking, storage, or production traffic without explicit confirmation.
Known limitations
- Use official Kubernetes sources for general context; local container orchestration and cluster operations, configuration, records, values, states, and permissions require inspected evidence.
- Task-specific work requires current evidence for cluster version and context, namespaces and ownership, manifests and applied objects, workloads, services, ingress, storage, and configuration, RBAC and service-account evidence, events, status, logs, metrics, and rollout history, and backup, policy, and change approvals.
- Do not infer cluster state, resources, images, configuration, secrets, permissions, health, capacity.
Safety notes
- Minimize personal, customer, employee, financial, credential, and other sensitive data.
- Require explicit confirmation before applying or deleting resources, changing images, configuration, secrets, access, scaling, networking, storage, or production traffic.
- Route legal, privacy, security, compliance, financial, employment, and other qualified judgments to accountable reviewers.