1 year ago

In today’s fast paced world, every second counts and the ability to react to activities in a timely fashion can mean the difference between satisfying the needs of consumers and meeting Service-Level Agreements. Automation and Kubernetes go hand in hand and Ansible already plays a role within this ecosystem.

This includes Ansible Core, the tooling associated with Event-Driven Ansible, and the Collection containing the Event-Driven Ansible Kubernetes integration.

With the rulebook monitoring for ConfigMap changes in the default namespace, create a new ConfigMap in the default namespace to demonstrate events are being captured appropriately.

kubectl delete configmap -n default eda-example kubectl create configmap -n default eda-example --from-literal=message=”Kubernetes Meets Event-Driven Ansible”