K8s Resource Visualizer

What is the K8s Resource Visualizer?

The K8s Resource Visualizer is a client-side tool that parses your Kubernetes YAML manifests and builds a resource relationship graph. It shows how Deployments, Services, Pods, ConfigMaps, Secrets, and Ingress resources are connected — displaying the topology as an indented tree structure for quick understanding of your cluster architecture.

How to Use

1. Paste your Kubernetes YAML manifests into the input field (multi-document YAML supported)
2. Click "Visualize" or wait for automatic processing
3. Review the resource relationship graph showing how resources are connected
4. Copy the graph output for documentation or sharing

Example: Application Stack

This multi-document manifest shows a typical web application with connected resources:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: web-ingress
spec:
  rules:
    - host: app.example.com
      http:
        paths:
          - path: /
            pathType: Prefix
            backend:
              service:
                name: web-service
                port:
                  number: 80
---
apiVersion: v1
kind: Service
metadata:
  name: web-service
spec:
  selector:
    app: web-app
  ports:
    - port: 80
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: web-app
  labels:
    app: web-app
spec:
  selector:
    matchLabels:
      app: web-app
  template:
    metadata:
      labels:
        app: web-app
    spec:
      containers:
        - name: web
          image: nginx:1.25

Detected Relationships

• Ingress → Service — Ingress routes external traffic to Services via backend rules
• Service → Pods/Deployments — Services route traffic to Pods matching their label selector
• Deployment → ReplicaSet — Deployments manage ReplicaSets via matchLabels
• ReplicaSet → Pod — ReplicaSets manage Pods via label selectors
• Workload → ConfigMap — Workloads use ConfigMaps via volumes or envFrom
• Workload → Secret — Workloads use Secrets via volumes, envFrom, or valueFrom

Reading the Graph Output

The graph is displayed as an indented tree. Root nodes (typically Ingress or Services with no incoming connections) appear at the top level. Child resources are indented below with tree connectors. Labels like [routes-to], [manages], and [uses] indicate the type of connection between resources.

Performance for Large Manifests

For manifests larger than 50KB, graph building is automatically offloaded to a Web Worker to keep the UI responsive. This means you can visualize complex multi-service architectures without the page freezing. Input is limited to 5MB maximum.

Use Cases

• Understand relationships in unfamiliar Kubernetes deployments
• Verify that Services correctly target the intended Pods
• Check that Ingress rules point to the right Services
• Confirm ConfigMap and Secret references are correct
• Document cluster topology for team onboarding
• Review pull requests that modify multiple K8s resources

Privacy and Security

All processing happens entirely in your browser using JavaScript. Your Kubernetes manifests — which may contain internal service names, namespace details, environment variables, and infrastructure topology — are never transmitted to any server. No data is stored, logged, or shared.