Ops by Pull Request: An Ansible GitOps Story
summary
Claims that using Ansible Tower webhooks turns Git commits into deployments without a separate CI trigger, wiring GitHub/GitLab repos to job templates and workflows. Demonstrates an agentless GitOps flow that scales a Kubernetes-backed caching app via an operator and an Ansible playbook, changing from two to five memcache nodes (then back to three) by committing a config file. Notes practical gaps: Kubernetes credentials/secrets handling and missing Kubernetes client libraries in Tower need work.
AI-written summary · about
chapters (11)
- 0:00Start
- 6:43Principles of Get-Ups
- 8:33What Is a Software Agent
- 9:04Get Ops Workflow
- 13:20Review of Ansible
- 15:43Get Centric Ansible Deployment Workflow
- 17:11Ansible Tower 3 6
- 19:58What Are the Advantages Here of Using Ansible
- 25:08Demo
- 27:11Kubernetes Cluster
- 38:17Handling of Kubernetes Credentials and Secrets
related talks
23mA Tall Tale of GitOps
35mGitOps - Operations by Pull Request
45mGitops: The Kubernetes way
15mGitOps in the Real World: Opportunities for Developer Experience Improvement
02h 02mAn end-to-end GitOps Architecture: Terraform, Ansible, Kubernetes and AWS
47mGitOps - Using Git as your source of truth for build, deploy and observability
31mLeveraging GitOps to wrangle your clusters and projects
01h 19mTutorial: Everything You Need To Become a GitOps Ninja