fix: remediate 13 VlamGuard policy failures

[github-actions]

Summary

The Deployment evident-risk in production has critical security risks (privileged container, root execution, mutable root filesystem, and privilege escalation) and high-availability gaps (single replica, no probes, and no resource limits). These issues expose the cluster to container breakout attacks, unauthorized access, and downtime risks. Immediate remediation is required for production safety.

VlamGuard Report

	Risk Score	Risk Level	Grade	Hard Blocks
Before	100/100	critical	C	5
After	100/100	critical	C	5

Fixes Applied

Check ID	File	Description
security_context	demo/charts/evident-risk/values.yaml	Applied static remediation: securityContext
resource_limits	demo/charts/evident-risk/values.yaml	Applied static remediation: limits
replica_count	demo/charts/evident-risk/values.yaml	Applied static remediation: replicaCount
readonly_root_fs	demo/charts/evident-risk/values.yaml	Applied static remediation: readOnlyRootFilesystem
service_account_token	demo/charts/evident-risk/values.yaml	Applied static remediation: automountServiceAccountToken
allow_privilege_escalation	demo/charts/evident-risk/values.yaml	Applied static remediation: allowPrivilegeEscalation

Unfixed (Manual Action Required)

• image_tag
• run_as_user_group
• liveness_readiness_probes
• image_pull_policy
• pod_security_standards
• drop_all_capabilities
• image_registry_allowlist

Related Issue

Closes #49

---

Generated by VlamGuard