---
schema_version: 1
route: /t/kubectl.md
tool: "kubectl"
---

# sincecutoff.com /t/kubectl — kubectl

- name: kubectl
- kind: cli
- children: none
- homepage: <https://github.com/kubernetes/kubectl>

Changes to the tools coding agents drive, since a model's training cutoff, each linked to its first-party source. Check installed versions and limitations before acting; a cutoff date does not establish what a model knows.
Original editorial content: [Apache 2.0](https://sincecutoff.com/v1/data-license.txt), by [0xPatrick](https://0xpatrick.dev). Preserve applicable license and [NOTICE](https://sincecutoff.com/notice.txt) attribution when redistributing. Third-party source text and examples retain their own rights. [License scope and attribution](https://sincecutoff.com/v1/license.json).
To stay current, read the changes feed: [`/v1/changes.md?tool=kubectl`](https://sincecutoff.com/v1/changes.md?tool=kubectl) (or `.json`), adding `since=YYYY-MM-DD` for your training cutoff. Entries for registered children are included; the registry itself is `/v1/tools.json`. How to page and save your place: [llms.txt](https://sincecutoff.com/llms.txt).

### kubectl explain --recursive accepts --max-depth (2026-08-26)
- slug: kubectl-explain-recursive-accepts-max-depth-b08a519ce489
- score: 0.93

How to use it:

When you need to inspect a resource schema recursively but limit nested fields, run `kubectl explain <resource> --recursive --max-depth=<depth>`.

Examples:

```
kubectl explain pods --recursive --max-depth=2
```

- why_it_matters: Limit nested fields while inspecting an API resource's schema recursively.
- sources: <https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.37.md#v1370>, <https://kubernetes.io/docs/reference/kubectl/generated/kubectl_explain/>
- gotchas: "Version: v1.37.0"; "<resource> (required): Resource type to explain; use `kubectl api-resources` to list supported resources."; "--recursive (required): Print fields of fields. Required when `--max-depth` is greater than 0."; "--max-depth (required): Maximum recursion depth when printing nested fields with `--recursive`; 0 means no limit."

### kubectl diff adds show-secret flag (2026-04-22)
- slug: kubectl-diff-adds-show-secret-flag-bac4e0676b16
- score: 0.93

How to use it:

When reviewing a diff that must display Secret values, run `kubectl diff` with `--show-secrets` and a manifest path. The v1.36 source uses the plural flag; the release note uses the singular form.

Examples:

```
kubectl diff --show-secrets -f <manifest>
```

- why_it_matters: Review a diff that includes Kubernetes Secret values.
- sources: <https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.36.md#v1360>, <https://github.com/kubernetes/kubernetes/blob/release-1.36/staging/src/k8s.io/kubectl/pkg/cmd/diff/diff.go>, <https://kubernetes.io/docs/reference/kubectl/generated/kubectl_diff/>
- gotchas: "Version: v1.36.0"; "--show-secrets: Boolean flag; when true, do not mask Secret values in the diff. Defaults to false."; "-f, --filename <manifest> (required): Filename, directory, or URL containing configuration to diff."; "The flag explicitly allows secret values to be displayed during the diff operation."; "Docs conflict: Release note and card say `show-secret`; v1.36 source and current generated docs document `--show-secrets` (plural)."