Why are CPU and memory limits essential in Kubernetes?

Containers without resource limits can monopolize worker node CPU and memory, starving other colocated pods and triggering kernel OOM (Out of Memory) kills.

What is the difference between liveness and readiness probes?

Liveness probes tell Kubernetes when to restart a deadlocked container. Readiness probes determine when a container is ready to accept incoming traffic from a Service.

Are my Kubernetes manifests kept private?

Yes. All YAML parsing and static rule auditing execute 100% locally in your web browser with zero server uploads.

Kubernetes Manifest Inspector

Audit multi-document Kubernetes YAML manifests for container security contexts, CPU/memory limits, readiness/liveness health probes, and deployment hygiene.

100% Client-Side Privacy

Security Score 100 / 100

Total Resources 0

Critical Security 0

Warnings 0

Kubernetes YAML (Multi-Doc) 0 docs

Frequently Asked Questions

Does this tool support multi-document YAML manifests?

Yes. Any manifest containing multiple Kubernetes resources separated by standard --- dividers is parsed into individual resource documents and audited in a single pass.

Which Kubernetes resources are inspected?

The auditor evaluates Pods, Deployments, StatefulSets, DaemonSets, Services, Ingresses, and Jobs, examining pod templates, container specifications, and security policies.

Why is allowPrivilegeEscalation: false recommended?

By default in Linux containers, child processes can gain more privileges than their parent (e.g. via setuid binaries). Setting allowPrivilegeEscalation: false blocks this privilege elevation pathway.

Are my cluster manifests sent to an external server?

No. 100% of parsing and policy validation executes client-side in your web browser tab.