Git based application deployment patterns for Kubernetes Git ❤ K8s 

Shahidh K Muhammed @shahidh_k 

Git ● Distributed version control system ● Manage source code ● Any text files can be tracked ● Collaboration 

Git - Source of Truth ● Infrastructure as Code ○ Terraform, CloudFormation ● System Configuration as Code ○ Ansible ○ Chef ○ Puppet ● Application Configuration as Code ○ Kubernetes ○ Hasura ● Application Source Code 

Declarative tools ❤ Git 

Ops ● Configure, build, test, deploy ● CI/CD ● Monitor, fix ● Upgrades ● Rollbacks ● Automation 

GitOps ● Ops practices using Git ● Use Git as source of truth ● Drive operations through git repo ● Get version control, history, peer review, and rollback ● Continuous delivery - Automated pipelines ● Webhooks: push to trigger build/test ● PRs & merge branch to deploy 

GitOps - Patterns ● CI builds artifacts ● Updates config (in a git repo) ● Trigger rollout (PR merge/commit) ● Observe ● Control 

GitOps - Patterns Source: Weave Works 

GitOps - Patterns ● Use declarative configuration to define application and services ● All changes go through git review process, none using kubectl ● Use an operator in the cluster to drive observed state to desired state, as declared by the configuration in git ● pre-push hook to create manifests ○ Render templates for correct env ○ Secrets ● pre-receive hook or webhooks to build artifacts and do kubectl set-image ● Power to developer ● Own tooling 

Shahidh K Muhammed @shahidh_k Thanks for listening! Questions?