The PR Is the UI: Simplifying Argo for Developers
summary
Priceline turns the Pull Request into the single deployment UI, wiring Argo Workflows, Argo CD, Argo Rollouts and Argo Events into an internal API that posts status, aborts syncs, rolls back canaries and accepts slapprove canary commands; the system serves 100K PRs of feedback, uses a dynamic rollout progress bar and a golden Helm chart to enable full-featured notifications and automated merges, and reports that the end-to-end flow and canary rollbacks work in production.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 1:01Priceline’s mission and Kubernetes
- 1:44Centralized Kubernetes at Priceline
- 3:30GitOps limitations for developers
- 4:32PRs as deployment UI
- 5:35Demo: regular deployment
- 6:17Approval bot and security
- 7:20Argo CD integration and hooks
- 8:02Real-time errors and rollback
- 9:07Production deployment with canary
- 10:10Canary failures and rollback
- 10:53Manual canary approval
- 11:34Dynamic rollout tracking
- 12:17Automated smoke testing
- 13:19Lessons learned and safety
- 14:43Building developer product
- 15:46Challenges and project insights
- 16:32PRs for resource actions
- 17:57Multi-region deployments and limits
- 19:20Future PR-driven deployments
- 20:23PRs for non-Kubernetes
- 21:29PRs as bot interaction hub
- 22:53Q&A
related talks
24mArgo Rollouts from the Trenches – Next Level Progressive Delivery Best Practices
25mSpace-Age GitOps: The Rise of the Humble Pull Request
25mHow to Multiply the Power of Argo Projects By Using Them Together
08mProject Updates: Argo CD
29mWelcome + Project Update
18mTailored Deployment Strategies: Argo Rollouts for Diverse Applications
31mGitOps, the Final Frontier: Proposing, Promoting, and Reverting
49mArgo Roadmap Updates For CD, Rollouts, Workflows, and Events
