Kubernetes Security and Governance made easy using Otomi
summary
Otomi installs via Helm and ties Helm + GitOps (git commits + Drone CI) to deploy Calico, OPA Gatekeeper, Istio and Harbor and ships prebuilt configs so teams avoid hand‑written YAML. Demo shows a privileged pod with hostPath denied once enforces PodSecurity and OPA Gatekeeper policies is enabled, HTTP egress is blocked after Otomi deploys a default Istio sidecar with outboundTrafficPolicy=REGISTRY_ONLY, and namespace network policies flip from deny‑all to selective whitelists — all working end to end.
AI-written summary · about
chapters (7)
- 0:00Session introduction
- 2:26Agenda and platform overview
- 4:03Container security demo
- 5:57Implementing security policies
- 8:13Network egress control
- 10:32Inter-pod communication
- 15:24Conclusion and community
related talks
28mEmbracing change: Policy-as-code for Kubernetes with OPA and Gatekeeper
32mSecuring our clusters with gatekeeper and OPA
30mSecuring the Kubernetes Empire with OpenPolicyAgent and Rego
10mThe Power of OPA Gatekeeper: Enforcing Kubernetes Access Control to secure your runtime
27mEmbracing change: Policy-as-code with OPA and Gatekeeper
34mEmbracing Change, Policy as code for Kubernetes with OPA and Gatekeeper
27mSecure Multicluster Istio Configuration Using GitOps...
26mBeyond Security: Leveraging OPA for FinOps in Kubernetes - Sathish Kumar Venkatesan