Free local check · No signup · No daily quota
Kubernetes Manifest Security Checker
Paste rendered Kubernetes manifests to find risky Pod settings before deployment. Review container privileges, host access and hardening gaps, with a partial Pod Security Standards estimate for each workload.
Quick answer
A Kubernetes manifest security checker reviews Pod settings before deployment. Paste one or more YAML documents to inspect container privileges, host access, capabilities and security contexts locally. Findings separate Pod Security Standards controls from additional hardening advice. The result covers selected checks and does not certify cluster admission compliance.
Review your YAML
YAML is processed in this tab. It is not uploaded or saved by this tool. Input and results are masked from session replay. Prefer redacted configuration.
Safer configuration pattern
Adapt this Linux Pod-spec fragment to your application. These settings address selected Restricted controls; the complete policy includes additional requirements. A read-only root filesystem is additional advice. Resource values and writable mounts must be chosen for the workload.
spec:
automountServiceAccountToken: false
securityContext:
runAsNonRoot: true
seccompProfile:
type: RuntimeDefault
containers:
- name: app
image: example/app:version
securityContext:
allowPrivilegeEscalation: false
readOnlyRootFilesystem: true
capabilities:
drop: [ALL]Related tools and guides
Frequently asked questions
Which workloads can I check?
The checker reads Pod, Deployment, StatefulSet, DaemonSet, ReplicaSet, Job and CronJob documents, including init and ephemeral containers. Separate manifests with a YAML document separator. Other kinds are reported as skipped when a supported workload is present.
Does the PSS estimate prove my workload is compliant?
No. It estimates Privileged, Baseline or Restricted for selected controls only. Other PSS controls, cluster versions, namespace policy and admission mutations can change the actual result. Use Kubernetes Pod Security Admission to verify the complete policy.
Are all findings Pod Security Standards violations?
No. Resource requests and limits, image tags, read-only root filesystems, token automount and inline-secret heuristics are outside PSS. They are labeled separately. Baseline and Restricted findings identify the relevant policy level.
Do Pod-level settings count for containers?
For runAsNonRoot and seccomp, allowed Pod-level settings can satisfy container requirements when the container does not override them. Explicit runAsUser zero is flagged at either level. The Linux-only Restricted checks for escalation, seccomp and capabilities are relaxed when spec.os.name is windows.
Is my YAML uploaded or stored?
The check runs in your browser without uploading or saving the YAML. Input and results are masked from session replay. Inline environment values with secret-like names are not echoed in findings. Use redacted manifests and clear the editor when finished.
Can I paste Helm templates or YAML anchors?
Render Helm templates before checking. This dependency-free reader supports common block YAML, single-line flow lists and maps, and literal or folded script blocks. Anchors, aliases, merge keys, tags and multiline flow or quoted/plain scalars produce errors. This is not a Kubernetes schema validator.