Summary
productionprofile (explicit)
0findings
0HIGH
0MEDIUM
0changes
0+ 0-resources added / removed
Before: fixtures/k8s/hardened.yaml · After: fixtures/k8s/hardened.yaml · profile blocks on HIGH, MEDIUM
Findings
No findings under the supported rules.
Changes (desired state, not live drift)
No differences in supported fields.
Blast radius
Questions to answer before release, and edges derived only from the manifests you supplied. Anything else is UNKNOWN.
- No changed tracked fields.
No dependency edges found in the supplied manifests.
Rollback prerequisites
| Prerequisite | State |
|---|---|
| Evidence of known previous deployable revision | DECLARED_NOT_VERIFIED |
| Independent backup validity evidence | DECLARED_NOT_VERIFIED |
| Actual successful restore test evidence | DECLARED_NOT_VERIFIED |
| Documented rollback sequence | DECLARED_NOT_VERIFIED |
| Independent authorized operator approval evidence | DECLARED_NOT_VERIFIED |
Rollback readiness is not established by declarations alone; a restore drill and human sign-off are required
Verification boundaries
| Check | State |
|---|---|
manifestParsing | VERIFIED_STATIC |
policyRules | VERIFIED_STATIC |
environmentDrift | NOT_TESTED |
liveRBAC | NOT_TESTED |
clusterDryRun | NOT_RUN |
workloadHealth | NOT_RUN |
realRollback | NOT_RUN |
humanApproval | NOT_VERIFIED |
Limitations
- This compares two local desired-state snapshots, not observed live drift.
- The built-in YAML parser supports a strict subset (no anchors, tags, templates, block scalars or nested flow collections); unsupported syntax fails loudly.
- Policy checks are heuristic static rules, not authoritative validation, admission control or compliance certification.
- Admission mutation, defaulting, controllers, image tag drift and real traffic exposure are not modelled.
- Dependency edges come only from the supplied manifests; anything else is reported UNKNOWN.
- No Kubernetes/cloud connection, deployment, destructive command, or rollback was executed.