inspect-kubernetes-relationships4.72 KB
View saved version →
---
name: inspect-kubernetes-relationships
description: Review supplied local Kubernetes YAML with Nexo YAML Iron when the user needs declared workload, Service, Ingress or resource-reference relationships and explicit unknown evidence. Use detailed inspection for underlying facts and joins. Do not use this as evidence of live cluster state, policy compliance or runtime health.
---
# Review Kubernetes Relationships
Use the executable bundled with this plugin as the authoritative analyzer. Explain
its structured results without computing, filling, relabeling or replacing Nexo
state from intuition. This release requires local execution on macOS ARM64.
## Locate the executable
Use `${PLUGIN_ROOT}/scripts/nexo-yaml-iron` when the host supplies a resolved plugin
root. If that variable is not defined, derive the root from the actual installed
location of this file: `skills/inspect-kubernetes-relationships/SKILL.md` is two
levels below it. Use that absolute root with `/scripts/nexo-yaml-iron`. Do not
substitute a same-named command from PATH or a development checkout.
If the host cannot execute local programs or the platform is unsupported, explain
the compatibility requirement and stop rather than guessing a result.
## Run the review
For a manifest path explicitly supplied or authorized by the user:
```sh
"${PLUGIN_ROOT}/scripts/nexo-yaml-iron" review <path>
```
If the user supplies YAML text, use the host's local file tools to place the exact
text in a temporary YAML file before invoking the executable. Preserve its document
boundaries and values. Do not add a namespace, rewrite fields or scan unrelated
files. Redact credential values before they are supplied; opaque output is not
redaction of content already sent to an AI host. Do not split oversized input to
bypass the 512 KiB file budget.
Present this compact Review result first, preserving established findings and
explicit unknowns. No reported finding is not a safety or completeness verdict.
## Coverage
Supported declaration kinds are Pod, Deployment, ReplicaSet, StatefulSet,
DaemonSet, Job, CronJob, Service, Ingress, ConfigMap, Secret, ServiceAccount,
PersistentVolumeClaim and Namespace. Coverage concerns supported fields and
relationships, not complete Kubernetes semantics. Keep actual workload kinds and
namespace-qualified identifiers attached to the explanation.
ConfigMap text, key references, container environment sources, mounts, volumes,
ServiceAccounts and named resource dependencies can be inspected where supported.
Explain only supplied text and established reference relationships. Do not infer
runtime environment expansion or precedence. Secret payloads and binary values
remain opaque in structured output; do not ask for real credentials.
Unsupported kinds or fields remain outside coverage. Init-container port evidence
is unknown in this slice. Missing supplied declarations do not prove cluster absence.
## Detailed inspection
Use Inspect when the user needs underlying evidence, complete joins or a deeper
view of ambiguous Service-port/backend evidence:
```sh
"${PLUGIN_ROOT}/scripts/nexo-yaml-iron" inspect <path> --format json
```
Review is a compact projection and does not enumerate every established
relationship. Preserve relevant Inspect evidence when Review omits a summary.
Use `--format ndjson` only when row-oriented output is useful. Add `--snapshot`,
`--partition` or `--namespace` only for requested artifact coordinates; these flags
do not supply a missing manifest namespace or establish live cluster state.
## Explain the evidence
- Preserve findings, unknowns, source keys, namespaces, route bindings and gap cases.
- A known witness can coexist with residual unknowns. Do not erase either one.
- An unknown does not establish a negative finding. A removed gap does not prove repair.
- Explain ConfigMap references from supplied facts; do not invent unseen values.
- If a diagram helps or the user requests one, show a small relevant relationship
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 1 — file references are metadata, not package contents.