AWS / kops Deep Dive / Hacking Session – Justin Santa Barbara, FathomDB

on YouTube ↗01h 11m

" summary

Walks through how kops contributions actually get merged: contributors hit a CLA requirement, PRs trigger end-to-end CI on AWS (including costly cluster tests), size and unit/integration tests determine review effort, and merge bots enforce LGTM→approve bot flow; ownership is gated by per-directory owners/approver model, so cross-dir changes need multiple approvals. Shows a real PR (deepmerge copied from Helm), common hiccups (needs rebase, flaky E2E, missing release-note), and a planned fix idea (inject secret hash into launch user-data to force rolling updates).

AI-written summary · about

" chapters (12)

1. 0:00Introduction
2. 11:48CLA
3. 15:14Test Infrastructure
4. 25:33Release Notes
5. 27:33Squashing commits
6. 30:03Will there
7. 30:53Undo
8. 34:18Owners
9. 45:13Extras Repository
10. 51:53Good Starter Issues
11. 53:53Rolling Updates
12. 55:03Live Coding

" related talks

• 35mGitOps in ActionJimmy Dahlqvist · Øredev 2019
• 28mBuilding K8s on AWS & Enabling Developers to Deliver. What to Do Better - Greg Sansom & Fahad TariqGreg Sansom, Fahad Tariq · Kubernetes Forum Sydney 2019
• 23mKubernetes GitOps on AWSJason Umiker · AWS Summit Online 2020
• 53mBirds of a FeatherMichael Hausenblaus · AWS Container Day 2019 San Diego
• 30mMerging Quickly in a Cloud Native WorldLucas Roesler · KubeCon + CloudNativeCon Europe 2019
• 23mKubernetes GitOps on AWSJason Umiker · AWS Summit Online EMEA 2020
• 29mTales from the Branches: GitOps in the Real WorldDan Garfield · GitOpsCon North America 2021
• 26mGitOps: yea or nay?Ricardo Castro · DevOpsDays Seattle 2021