Optimize Kubernetes on vSphere with Event-Driven Automation
summary
A downloadable appliance called VMware Event Broker Appliance listens to vCenter, converts vSphere alarms and the 1800+ vSphere events into CloudEvents + Knative payloads, and runs small functions on Kubernetes to notify Slack, enrich alarm data, or trigger remediation. Demos show it detecting live VMotion migrations and posting Slack alerts; the project connects one vCenter per appliance, runs on Kubernetes, and handles hundreds/sec tested throughput in practice.
AI-written summary · about
chapters (18)
- 0:00Start
- 4:59Who Runs Kubernetes on Vsphere
- 5:59Event Driven Architecture
- 6:20What Is an Event
- 8:47Use Cases for Event Driven Systems
- 9:40Automation Use Cases
- 12:01Vmware Event Broker Appliance
- 12:20The Vmware Event Broker Appliance
- 15:29Use Cases
- 17:33Vmotion Live Migration
- 19:58Kubernetes Environment
- 20:23Detecting and Sending Something To Slack
- 23:47The Kubernetes Control Plane
- 25:46Vsphere Alarms
- 26:09Alarms and Vsphere
- 30:45Vsphere Environment
- 31:43Alarm Info
- 40:29Correlating Events for Multiple Layers of Vsphere
related talks
33mKubernetes VMware User Group Intro: Best Practices for Running on VMware
31mElephant in the room
19mEvent Discovery for Kubernetes Applications
16mVMware and Chef, What's the Ecosystem Like, Where Does Everything Fit?
43mKubernetes in VMware
27mIntro: SIG VMware
50mAutomating Kubernetes with Event Driven Ansible
45mDeep Dive: SIG VMware
