Automated Policy-Based Service Assurance in Cloud-Native...
summary
An end-to-end closed loop is implemented: EMCO policy controller deploys agents that use Prometheus metrics and enrich events, sends KPIs to OPA as policy engine, and invokes Temporal workflows as the actor. A declarative intent ties an OPA rule (memory-usage threshold) to a workflow that migrates an application between two Kubernetes clusters. The live demo triggers the rule after changing the threshold and successfully terminates pods in cluster1 and brings them up in cluster2.
AI-written summary · about
chapters (8)
- 0:00Start
- 0:30EMCO Overview
- 2:00EMCO Background
- 3:16Intro to Temporal
- 6:13Open Policy Agent: Overview
- 7:10EMCO Policy Controller
- 9:51Policy Controller - Temporal Workflow Integration
- 10:21Policy Controller - OPA- Temporal: Closed Loop Flow
related talks
38mOPA for the cloud natives
19mDynamic Authorization and Policy Control for Your Kubernetes Cluster
36mOPA for the cloud natives
25mPolicing Your Kubernetes Clusters with Open Policy Agent (OPA) - Mark Puddick & Amith Nambiar
34mUnit Testing Your Kubernetes Configurations Using Open Policy Agent
20mDeep Dive: Kubernetes Policy WG
27mEmbracing change: Policy-as-code with OPA and Gatekeeper
09mSecure UI + Microservices within Kubernetes using OPA Authorization
