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.
cluster-template
A template for deploying a Talos Kubernetes cluster including Flux for GitOps
terraform-kubestack
Kubestack is a framework for Kubernetes platform engineering teams to define the entire cloud native stack in one Terraform code base and continuously evolve the platform safely through GitOps.
pepr
Type safe K8s middleware for humans
Solidvessel
A shopping application designed with microservices architecture
homelab-iac
Infrastructure as Code files for homelab cluster. Mirror of https://gitlab.wuhoo.xyz/jerry/homelab-iac
automata
Monorepo for Starjunk and subsidiaries
ansible-k3s-argocd-renovate
K3s Kubernetes for ZFS with ArgoCD & Renovate for GitOps via Ansible
aws-sandbox
Experiment with different Infra-as-Code design patterns, tools and the like using AWS environment resources
gitops-secrets-sample-app
GitOps example with Bitnami sealed secrets