Download as PDF, PPTX
Uploaded byBrice Fernandes
Speeding up your team with GitOps
This document presents an overview of GitOps, an operational model for speeding up teams utilizing Kubernetes and cloud native tools developed by Weaveworks. It outlines the principles of GitOps, such as declarative system descriptions, versioned desired state, and automated application of changes, which lead to improved deployment frequency and system reliability. Additionally, it highlights case studies demonstrating the effectiveness of GitOps in organizations, resulting in significant reductions in time to fix software bugs and enhance service uptime.
More Related Content
Similar to Speeding up your team with GitOps
Speeding up your team with GitOps
- 1. Speeding up your teamwith GitOps London SEAM – June 2019 Brice Fernandes – brice@weave.works 1
- 2. 2 I’m Brice I workfor Weaveworks. You can find Weaveworks at https://www.weave.works or @weaveworks Team at Weaveworks is behind the GitOps model. We build GitOps tools for enterprise Kubernetes and Cloud Native.
- 3.
- 4. 4 This talk Tactical Technical Process /tools Principles of Operations
- 5.
- 6.
- 7. 7 GitOps is... An operationmodel for
- 8. 8 GitOps is... An operationmodel Derived from CS and operation knowledge
- 9. 9 GitOps is... An operationmodel Derived from CS and operation knowledge Technology agnostic (name notwithstanding)
- 10. 10 GitOps is... An operationmodel Derived from CS and operation knowledge Technology agnostic (name notwithstanding) A set of principles (Why instead of How)
- 11. 11 GitOps is... An operationmodel Derived from CS and operation knowledge Technology agnostic (name notwithstanding) A set of principles (Why instead of How) Although Weaveworks can help with how
- 12. 12 GitOps is... An operationmodel Derived from CS and operation knowledge Technology agnostic (name notwithstanding) A set of principles (Why instead of How) A way to speed up your team
- 13.
- 14.
- 15. 15 GitOps ON Kubernetes Kubectl/ Direct access
- 16.
- 17.
- 18.
- 19. 19 Deployment Agent * GitOps ONKubernetes
- 20.
- 21.
- 22.
- 23.
- 24.
- 25. The Principles ofGitOps 25
- 26. 26 1 The entiresystem is described declaratively. 2 The desired system state is versioned 3 Approved changes to the desired state are automatically applied to the system 4 Software agents ensure correctness and alert on divergence
- 27. 27 GitOps ON Kubernetes Image Repository 1 Theentire system is described declaratively.
- 28. 28 GitOps ON Kubernetes Image Repository 2 Thedesired system state is versioned
- 29. 29 GitOps ON Kubernetes Image Repository 3 Approvedchanges to the desired state are automatically applied to the system
- 30. 30 GitOps ON Kubernetes Image Repository 4 Softwareagents ensure correctness and alert on divergence
- 31. What should beGitOps’ed? 31
- 32. What should beGitOps’ed? 32 I’m so very sorry
- 33.
- 34. Dashboards Alerts Playbook Kubernetes Manifests Application configuration Provisioningscripts 34 Application checklists Recording Rules Sealed Secrets
- 35. Dashboards Alerts Playbook Kubernetes Manifests Application configuration Provisioningscripts 35 Application checklists Recording Rules Sealed Secrets Technical / Application Domain
- 36.
- 37. Why should wecare? 37
- 38. Typical CICD pipeline ContinuousIntegration Cluster API Continuous Delivery/Deployment Container Registry CI Code Repo Dev RW CI credsGit creds RW CR creds3 RO RW API creds CR creds1 Shares credentials cross several logical security boundaries. Boundary RO RW Container Registry (CR) creds2
- 39. Cluster API GitOps pipeline Container Registry CI Code Repo DevRO CR creds2 CI credsGit creds RO Deploy CR creds3 RO RW Config repo creds CR creds1 Credentials are never shared across a logical security boundary. RW RW RW Cluster API creds Canonical desired state store Config Repo
- 40. Cluster API GitOps pipeline Container Registry CI Code Repo DevRO CR creds2 CI credsGit creds RO Deploy CR creds3 RO RW Config repo creds CR creds1 Credentials are never shared across a logical security boundary. RW RW RW Cluster API creds Operator RW Config Repo
- 41. Operator Cluster API GitOps pipeline Container Registry CI Code Repo DevRO CR creds2 CI credsGit creds RO Deploy CR creds3 RO RW Config repo creds CR creds1 Credentials are never shared across a logical security boundary. RW RW RW Cluster API creds RW Config Repo Process & constraints enforcement
- 42. Operator Cluster API GitOps pipeline Container Registry CI Code Repo DevRO CR creds2 CI credsGit creds RO Deploy CR creds3 RO RW Config repo creds CR creds1 Credentials are never shared across a logical security boundary. RW RW RW Cluster API creds RW Config Repo Exceptional auditing and attribution*
- 43. 43 ● Trivialises rollbacks ●Exceptional auditing and attribution* ● Separation of concerns ● No crossing security boundary ● Process & constraints enforcement ● Great Software ↔ Human collaboration point ● Easy to validate for correctness (Policies) ● System can self heal Why should we care?
- 44. 44 ● Trivialises rollbacks ●Exceptional auditing and attribution* ● Separation of concerns ● No crossing security boundary ● Process & constraints enforcement ● Great Software ↔ Human collaboration point ● Easy to validate for correctness (Policies) ● System can self heal Why should we care? * If you’ve secured your Git repositories properly
- 45.
- 46. 46 1) Estimated timeneeded to fix prod software bugs ~60% less time after switching 2) Estimated time to respond to customer requests ~43% less time after switching 3) Service uptime went to 100% from 99% Customer tools: Jenkins, GKE and Weave Cloud. Apps: web, ML. The GitOps effect
- 47. 47 The GitOps effect ~2→ 150+ deployments per week
- 48. 48 The GitOps effect ~2→ 150+ deployments per week Why?
- 49.
- 50.
- 51.
- 52.
- 53.
- 54.
- 55.
- 56. 56 Feedback loop latency. Thisis what matters.
- 57.
- 58.
- 59. BI dashboards BI Reports Playbook TeamMembership Org Chart Operations Manual 59 Security Policies Processes Roles & Authorisation
- 60. BI dashboards BI Reports Playbook TeamMembership Org Chart Operations Manual 60 Security Policies Processes Roles & Authorisation Business Domain
- 61.
- 62.
- 63.
- 64. 64 What if youcould roll back your sales processes? What if you could create a pull request on your organisation policy? What if you could get it reviewed and approved in an afternoon? What if your entire business could be reproduced the same way a git repository is cloned?
- 65.
- 66. 66 Kubernetes operator (Flux,Open Source) Multiple clusters (staging and prod) CD into staging Promotion from staging to prod Kubernetes Automated diff tools (*diff operators, Open Source) Dashboard definitions in Git (Grafanalib, Open Source) Alert definitions in git Read-only access to production for all developers Gated, PR-driven changes to production *“stress-reduced”
- 67.
- 68. 68 Kubernetes operator (Flux,Open Source) Multiple clusters (staging and prod) CD into staging Promotion from staging to prod Kubernetes Automated diff tools (*diff operators, Open Source) Dashboard definitions in Git (Grafanalib, Open Source) Alert definitions in git Read-only access to production for all developers Gated, PR-driven changes to production *“stress-reduced”
- 69.
- 70. 70 Kubernetes operator (Flux,Open Source) Multiple clusters (staging and prod) CD into staging Promotion from staging to prod Kubernetes Automated diff tools (*diff operators, Open Source) Dashboard definitions in Git (Grafanalib, Open Source) Alert definitions in git Read-only access to production for all developers Gated, PR-driven changes to production *“stress-reduced”
- 71.
- 72.
- 73. 73 Kubernetes operator (Flux,Open Source) Multiple clusters (staging and prod) CD into staging Promotion from staging to prod Kubernetes Automated diff tools (*diff operators, Open Source) Dashboard definitions in Git (Grafanalib, Open Source) Alert definitions in git Read-only access to production for all developers Gated, PR-driven changes to production *“stress-reduced”
- 74.
- 75.
- 76.
- 77.
- 78.
- 79.
- 80. 80 Kubernetes operator (Flux,Open Source) Multiple clusters (staging and prod) CD into staging Promotion from staging to prod Kubernetes Automated diff tools (*diff operators, Open Source) Dashboard definitions in Git (Grafanalib, Open Source) Alert definitions in git Read-only access to production for all developers Gated, PR-driven changes to production ⇒ *“stress-reduced”
- 81. 81 Kubernetes operator (Flux,Open Source) Multiple clusters (staging and prod) CD into staging Promotion from staging to prod Kubernetes Automated diff tools (*diff operators, Open Source) Dashboard definitions in Git (Grafanalib, Open Source) Alert definitions in git Read-only access to production for all developers Gated, PR-driven changes to production ⇒ < 30 minute total disaster recovery
- 82. 82 Kubernetes operator (Flux,Open Source) Multiple clusters (staging and prod) CD into staging Promotion from staging to prod Kubernetes Automated diff tools (*diff operators, Open Source) Dashboard definitions in Git (Grafanalib, Open Source) Alert definitions in git Read-only access to production for all developers Gated, PR-driven changes to production ⇒ < 30 minute total disaster recovery Dozens of changes per day with a very small team
- 83. 83 Kubernetes operator (Flux,Open Source) Multiple clusters (staging and prod) CD into staging Promotion from staging to prod Kubernetes Automated diff tools (*diff operators, Open Source) Dashboard definitions in Git (Grafanalib, Open Source) Alert definitions in git Read-only access to production for all developers Gated, PR-driven changes to production ⇒ < 30 minute total disaster recovery Dozens of changes per day with a very small team Incredibly fast regression response
- 84. 84 Kubernetes operator (Flux,Open Source) Multiple clusters (staging and prod) CD into staging Promotion from staging to prod Kubernetes Automated diff tools (*diff operators, Open Source) Dashboard definitions in Git (Grafanalib, Open Source) Alert definitions in git Read-only access to production for all developers Gated, PR-driven changes to production ⇒ < 30 minute total disaster recovery Dozens of changes per day with a very small team Incredibly fast regression response Permissive approach to production access
- 85. 85 Kubernetes operator (Flux,Open Source) Multiple clusters (staging and prod) CD into staging Promotion from staging to prod Kubernetes Automated diff tools (*diff operators, Open Source) Dashboard definitions in Git (Grafanalib, Open Source) Alert definitions in git Read-only access to production for all developers Gated, PR-driven changes to production ⇒ < 30 minute total disaster recovery Dozens of changes per day with a very small team Incredibly fast regression response Permissive approach to production access Excellent developer experience
- 86. 86 Kubernetes operator (Flux,Open Source) Multiple clusters (staging and prod) CD into staging Promotion from staging to prod Kubernetes Automated diff tools (*diff operators, Open Source) Dashboard definitions in Git (Grafanalib, Open Source) Alert definitions in git Read-only access to production for all developers Gated, PR-driven changes to production ⇒ < 30 minute total disaster recovery Dozens of changes per day with a very small team Incredibly fast regression response Permissive approach to production access Excellent developer experience Stress-free on-call*
- 87. 87 Kubernetes operator (Flux,Open Source) Multiple clusters (staging and prod) CD into staging Promotion from staging to prod Kubernetes Automated diff tools (*diff operators, Open Source) Dashboard definitions in Git (Grafanalib, Open Source) Alert definitions in git Read-only access to production for all developers Gated, PR-driven changes to production ⇒ < 30 minute total disaster recovery Dozens of changes per day with a very small team Incredibly fast regression response Permissive approach to production access Excellent developer experience Stress-free on-call* *“stress-reduced”
- 88. Where to findout more 88 Search for “Weaveworks GitOps” in your favourite search engine Take a look at our opensource work on https://github.com/weaveworks Questions? Weaveworks @weaveworks https://weave.works Brice Fernandes @fractallambda brice@weave.works