Improve Container Management with Event-Driven Ansible
summary
Event-Driven Ansible connects to event sources like HTTP endpoints, Kubernetes and Kafka and automatically runs existing Ansible playbooks to perform remediation (e.g., listening to cluster events, scaling PVCs or qemu-in-k8s VMs). It integrates with GitOps by committing or opening pull requests, sends logs to ServiceNow, runs as a lightweight container (a few hundred MB RAM), and reduces real-world downtime from about six hours to automated fixes taking roughly four minutes.
AI-written summary · about
chapters (8)
- 0:00Event-Driven Ansible for containers
- 5:17What is Ansible
- 8:28Event-driven with Ansible
- 13:28Container management
- 17:47Kubernetes storage issues
- 24:39Production benefits
- 28:58Q&A
- 37:35Conclusion
related talks
50mAutomating Kubernetes with Event Driven Ansible
36mLeverage Event Driven Ansible to reduce your automation reaction time
39mContinuous Deployment with Ansible
29mOn-Containerized Ansible
36mMake You Ops-Life Easy – ansible usecases you didn´t out of track
33mProvisioning Docker Containers Using Ansible: The Good, the Bad and the Ugly
23mAnsible with Edge Computing
29mSimplifying container orchestration with Ansible and Podman