Organizing Teams for GitOps and Cloud Native Deployments
Talkat GitOpsCon Europe 2022 · on Tuesday, 2022-05-17· at 10:30· Pavilion 3 | Room E | Level 2 | Central Forum·
summary
Research shows improving processes raises velocity not slows it, driven by small batches and DORA metrics. Repos split by role (app, ops, platform) follow either shared or distinct patterns; an example pipeline stores artifacts, hydrates templated manifests into a deployment repo, and Argo/Flux/Config Sync continuously reconciles clusters. Use branch per non-production environment and pin prod with commit hash for prod or immutable tags. Enforce policies at CI, delivery, and with OPA Gatekeeper admission control.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:17Hi, I'm Sandeep
- 2:09Software Delivery & Operations Performance
- 8:25Team Roles
- 9:41Tenancy
- 10:37Single Tenant Clusters
- 11:27Multi Tenant Clusters
- 12:25Example Workflow
- 13:49Workflow Considerations
- 16:40Commits, Tags, Branches
- 21:00Supporting app teams
- 22:22Key Components
- 24:26Gatekeeper
- 26:23Shift Policy Enforcement Left
- 27:41Enforcing Guardrails
related talks
29mPutting the Ops in GitOps - New Challenges in Managing Cloud Native Environments
35mPanel: GitOps User Stories
35mGitOps - Operations by Pull Request
06mGitOps - At a Glance
28mManaging GitOps as a Platform Service
24mBest Practices for GitOps Promotions
21mGitOps: Where One Size Doesn't Fit All
45mFrom DevOps to GitOps: Supercharging Your Kubernetes Workload Deployments