Kubernetes Resource Reference Explorer

How to use Kubernetes Resource Reference Explorer

Trace selected Pod-template references and potential Service label matches across a supplied local manifest bundle. Review named ConfigMap, Secret, ServiceAccount and PVC references in one assumed namespace model. Distinguish objects present in the input from objects not supplied, without querying a cluster or returning configuration values.

1. Provide local resource bundle: json object/array, v1 list or yaml documents, assumed namespace when metadata.namespace is absent.
2. Choose the supported mode and run the tool. Review its assumptions and any reported errors.
3. Copy the result or download a separate output; reset to clear the current form.

Good to know

• 200 KB well-formed UTF-8; at most 100 flattened resources, 100 documents, four List-wrapper levels, 40 syntax levels, 30,000 YAML nodes, 2,000 selected references and 1,000 diagnostics. Container/volume/source lists and label maps have explicit local caps.
• YAML 1.2 core refuses aliases, merge/custom tags, duplicate keys and non-string keys; JSON refuses duplicate/prototype-related keys. Literal lower-case DNS-style resource names are required; generated names, templates and environment interpolation are not expanded.
• Selected v0.34 API shapes: core v1 Pod, ConfigMap, Secret, Service, ServiceAccount and PVC; apps/v1 Deployment/StatefulSet/DaemonSet/ReplicaSet; batch/v1 Job/CronJob. Other apiVersion/kind pairs are inventoried as unmodeled. Full Kubernetes schema/feature-gate validation is outside the profile.
• Only explicit env/envFrom, ConfigMap/Secret volumes and projections, imagePullSecrets, serviceAccountName and persistentVolumeClaim references are examined. Service label matches are candidates from supplied Pods/templates, not real endpoints or readiness. Admission defaults, controller-generated claims, inherited image-pull secrets, RBAC and port resolution are not simulated.
• Namespace is an explicit user assumption where absent. Not supplied does not mean missing from a cluster. Secret/ConfigMap values, commands and literal environment values are excluded from the report; only their selected key names can appear.
• A dedicated Worker prepares modules and the requested YAML parser for at most 10 seconds before ready; a separate 2-second computation deadline terminates it. No cluster, API URL, include file, Helm/Kustomize renderer or network resource is accessed.
• The separate JSON report is limited to 500,000 characters, including formatting; reduce the source if the report exceeds that bound.
• Inputs are processed on this device and are not automatically saved or uploaded.