Security and Policy
Admission and Policy Guardrails Workshop
Quality standards alignment through validating and mutating hooks with test harnesses operators can reuse.
- Duration
- 10 days
- Format
- Workshop week
- Tuition (informational)
- 890,000 KRW
Builds small policies with unit tests, stages them through namespaces, and rehearses failure when APIs are unavailable. Focus stays on operational safety, not policy language novelty.
What is included
- Webhook local test harness patterns
- Ordering pitfalls between multiple webhooks
- Dry-run integration with CI snippets
- Latency budgets for admission paths
- Fallback behaviors when webhook endpoints stall
- Documentation expectations for external reviewers
- Rollback cards for policy removals
Outcomes
- Ship a validating policy with tests and rollback card
- Explain webhook ordering to an application team
- Measure admission latency impact before rollout
Lead instructor
Sora Kim
Security-focused platform engineer; publishes small tools for policy linting.
Participant notes
-
“Latency budget module changed how we negotiate with security reviewers.”
— Yuki , Platform engineer · 5/5
Common questions
Languages?
Examples in Go for webhook servers; concepts apply elsewhere.
Included tools?
Cluster-side only; your IDE and local toolchain are yours to configure.
Support after?
Two weeks of forum access for clarifications, not production consulting.
Refund rules live under Returns & Refunds. No payments are processed on this marketing site.
Schedule a call