Claude Code statusline that shows the active kubectl context and namespace with a deployment-environment risk label.
Open the source and read safety notes before installing.
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
Decision playbook
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
0
78
—
No baseline selected
No major trust-signal divergence detected in the current selection.
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Source provenance statusRequired
Marked as source-backed.
Metadata reviewed
Registry metadata indicates a reviewed listing.
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Trust level risk gateRequired
Trust level does not block evaluation.
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Package verification flag
No package verification flag provided.
Checksum metadata
No checksum provided for downloaded artifact.
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
Baseline comparison available
No baseline peer selected yet.
Diverging trust signals identified
No major trust-signal divergence found.
Setup at a glance
Copy-ready — paste the snippet to get started.
Adoption plan
Current risk score 16/100. Use staged verification before broader rollout.
Validate source and review signals before any execution.
Confirm source provenanceRequired
Source URL/provenance metadata is present.
Confirm metadata review state
Listing has review metadata.
Verify install payload
Install/config payload exists and can be inspected.
Confirm safety, privacy, and package integrity signals.
Review safety notesRequired
Safety notes are present.
Review privacy notesRequired
Privacy notes are present.
Verify package integrity metadata
No package verification/checksum metadata.
Adopt in controlled steps based on the selected plan.
Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Evidence readiness
Required evidence gates are covered (5/6 signals complete).
Source repository/provenance is listed.
Required in this preset
Review metadata is present.
Required in this preset
Safety notes are present.
Required in this preset
Privacy notes are present.
Optional in this preset
Package integrity metadata is missing.
Optional in this preset
Install payload is available.
Required in this preset
Required evidence gates are covered for this preset.
Decision timeline
5/6 steps complete with no blocking gaps for this preset.
triage
Source/provenance metadata is available.
triage
Review metadata is available.
verify
Safety notes are available.
verify
Privacy notes are available.
verify
Package integrity metadata is missing.
rollout
Install payload is available.
No required blockers for this timeline preset.
Prerequisite readiness
3 prerequisites to line up before setup.
Safety & privacy surface
4 safety and 3 privacy notes across 2 risk areas.
#!/usr/bin/env bash
set -u
sanitize_status_value() {
printf '%s' "$1" | LC_ALL=C tr -cd '\040-\176'
}
main() {
if ! command -v kubectl >/dev/null 2>&1; then
echo "deploy: kubectl missing"
exit 0
fi
context=$(sanitize_status_value "$(kubectl config current-context 2>/dev/null || true)")
if [ -z "$context" ]; then
echo "deploy: no context"
exit 0
fi
namespace=$(sanitize_status_value "$(kubectl config view --minify --output 'jsonpath={..namespace}' 2>/dev/null || true)")
if [ -z "$namespace" ]; then
namespace="default"
fi
combined=$(printf '%s %s' "$context" "$namespace" | tr '[:upper:]' '[:lower:]')
if printf '%s' "$combined" | grep -Eq 'prod|production|live'; then
risk="high"
elif printf '%s' "$combined" | grep -Eq 'stage|staging|preprod'; then
risk="watch"
else
risk="dev"
fi
printf 'deploy: %s | ns %s | %s\n' "$context" "$namespace" "$risk"
}
case $- in
*n*) ;;
*) main "$@" ;;
esac{
"statusLine": {
"type": "command",
"command": "$CLAUDE_PROJECT_DIR/.claude/statuslines/kubectl-deployment-context-statusline.sh"
}
}kubectl config current-context and config inspection commands.Checked existing statuslines, live HeyClaude statuslines, open pull requests, and repository content for kubectl-deployment-context-statusline, deployment environment, kubectl context, namespace warning, and production context statuslines. Existing Kubernetes content appears in MCP and hook categories, but no statusline entry or open PR covers deployment context.
Editorial statusline recipe. No paid placement or affiliate link is used.
Show that kubectl Deployment Context Statusline is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/statuslines/kubectl-deployment-context-statusline)kubectl Deployment Context Statusline side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
1 trust signal differ across this comparison (Submitter).
| Field | Claude Code statusline that shows the active kubectl context and namespace with a deployment-environment risk label. Open dossier | Claude Code statusline that surfaces sensitive environment-file risk and can optionally run git-secrets as a local pre-commit-style scanner. Open dossier | Multi-provider AI performance dashboard with context occupancy tracking, truncation warnings, TTFT latency, tokens/min rate, and model comparison metrics. Open dossier | Claude Code statusline that estimates context pressure from local session token counts and a configurable context limit, then prints a compact risk tier. Open dossier |
|---|---|---|---|---|
| Next steps | ||||
| Trust | ||||
| Review status | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed |
| Package trust | Package not verified | Package not verified | Package not verified | Package not verified |
| Source provenance | Source-backed | Source-backed | Source-backed | Source-backed |
| SubmitterDiffers | MkDev11 | MkDev11 | — | MkDev11 |
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | — | — | — | |
| Category | statuslines | statuslines | statuslines | statuslines |
| Source | Source-backed | Source-backed | Source-backed | Source-backed |
| Author | MkDev11 | MkDev11 | JSONbored | MkDev11 |
| Added | 2026-06-04 | 2026-06-04 | 2025-10-23 | 2026-06-04 |
| Platforms | ||||
| Harness | ||||
| Source repo | — | — | — | — |
| Safety notes | ✓The script is read-only and does not contact workloads, apply manifests, or change namespaces. The displayed context and namespace are limited to printable ASCII before terminal output. Risk labels are based on names; confirm the actual cluster and namespace before deployment commands. Avoid running write-capable automation solely because the statusline says an environment looks like development. | ✓The default mode does not scan file contents; it only counts sensitive-looking environment files in Git status. Enable recursive git-secrets scanning only in repositories where you are authorized to inspect all files. Scanner mode invokes the git-secrets executable directly and does not fall back to Git aliases. Treat any scan warning as a stop-and-review signal before committing, sharing logs, or opening a PR. | ✓Runs as a Claude Code statusline command on every refresh and depends on the local shell environment; a failure only affects status rendering, not your session. | ✓Context percentage is only as accurate as the configured limit and the usage fields available in the statusline input. Use the warning as a cue to summarize or checkpoint work before context pressure affects reasoning quality. Do not treat a low percentage as proof that all relevant files, instructions, or tool results are still in scope. |
| Privacy notes | ✓Context and namespace names can expose customer, region, cluster, or service names in screenshots. kubectl reads local kubeconfig, which may reference private clusters and identities. The script does not print server URLs or certificates. | ✓The default output prints counts only and does not print filenames or matched values. Recursive scans read repository files and may inspect sensitive local material. Terminal recordings can still reveal that a workspace contains sensitive environment files. | ✓Reads the Claude Code statusline JSON from stdin (model, token usage, context occupancy) and renders it in the local terminal; it does not send data off-machine. | ✓The script reads local session counters and does not inspect prompt text, files, or transcript contents. Token counts and configured limits can still reveal workload size in screenshots or shared terminal logs. Teams should avoid placing customer names or project identifiers in shell variables that appear in debugging output. |
| Prerequisites |
|
|
|
|
| Install | — | — | — | — |
| Config | | | | |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Source-backed guides for putting this to work.
Write a claude-code-hint tag to stderr under CLAUDECODE, and Claude Code prompts users once to install your official-marketplace plugin.
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.