GitOps topic
GitOps is an operational framework that takes DevOps best practices used for application development such as version control, collaboration, compliance, and CI/CD, and applies them to infrastructure automation. GitOps uses Git repositories as a single source of truth to deliver infrastructure as code.
GitOps delivers:
- A standard workflow for application development
- Increased security for setting application requirements upfront
- Improved reliability with visibility and version control through Git
- Consistency across any cluster, any cloud, and any on-premise environment
Key components of a GitOps workflow
There are four key components to a GitOps workflow, a Git repository, a continuous delivery (CD) pipeline, an application deployment tool, and a monitoring system.
- The Git repository is the source of truth for the application configuration and code.
- The CD pipeline is responsible for building, testing, and deploying the application.
- The deployment tool is used to manage the application resources in the target environment.
- The monitoring system tracks the application performance and provides feedback to the development team.
monokle
Monokle is a set of OSS tools designed to help create and maintain high-quality Kubernetes configurations throughout the application lifecycle
gitops-using-argo-cd-and-tekton
GitOps using Argo CD and Tekton
sealed-secrets-web
A web interface for Sealed Secrets by Bitnami.
eks-hpa-profile
An eksctl gitops profile for autoscaling with Prometheus metrics on Amazon EKS on AWS Fargate
gh-actions-demo
GitOps pipeline with GitHub actions and Weave Cloud
gitops-app-distribution
GitOps workflow for managing app delivery on multiple clusters
gitops-progressive-delivery
Progressive delivery with Istio, Weave Flux and Flagger
cd-gitops-reference-architecture
Details of the CD/GitOps architecture in use at InfluxData
flytectl
A cross platform CLI for Flyte. Written in Golang. Offers an intuitive interface to Flyte https://docs.flyte.org/projects/flytectl/en/latest/