Upgrade to Pro — share decks privately, control downloads, hide ads and more …

GitOps: Operations by Pull-request

GitOps: Operations by Pull-request

This talk is based on https://www.weave.works/blog/gitops-operations-by-pull-request, I've presented this at Kubernetes meetup in San Francisco.

Ilya Dmitrichenko

September 27, 2017
Tweet

More Decks by Ilya Dmitrichenko

Other Decks in Technology

Transcript

  1. – gitops theory • any developer can use git •

    anyone can join team and ship a new app or make changes easily • all changes can be stored, audited and validated in git and we didn’t have to do anything very new or clever =)
  2. – gitops theory • config is code & everything is

    config (‘declarative infra’) • code (& config!) must be version controlled • CD tools that do not record changes in git are harmful
  3. – gitops theory Continuous Delivery/Deployment Image Repo Orchestrator Deploy Synchronizer

    Config change Manual deployment Git Code change Git Update Hint Continuous Integration Deploy Automator CI Pipeline
  4. – more gitops •everything is checked in git •easy to

    deploy the entire stack locally •easy to fork a cluster •easy to detect ad-hoc changes, alert/undo
  5. – more gitops •git is the source of truth •review

    process is the same as for code •infra changes go through review process •you are free to use whatever tools