GitOps
39 items tagged with "gitops"
Anti-Patterns4
Configuration Drift
Environments that should be identical gradually diverge as undocumented manual changes accumulate, breaking reproducibility and causing inconsistent behavior.
ClickOps
Provisioning and changing cloud infrastructure by hand through web consoles, producing undocumented, irreproducible, and unauditable configuration.
No Infrastructure as Code
Running infrastructure without any code-based definition, so it cannot be versioned, reviewed, reproduced, or recovered systematically.
Latest Tag in Production
Deploying container images by the mutable :latest tag, so production runs an unknown, changing version that cannot be reliably reproduced or rolled back.
Tutorials3
How to set up GitOps continuous delivery with Argo CD
Deploy and sync Kubernetes manifests from Git using Argo CD Applications with automated, self-healing syncs.
How to set up GitOps with Argo CD
Deploy applications to Kubernetes declaratively by syncing manifests from Git using Argo CD.
How to implement GitOps with Flux
Bootstrap Flux into a Kubernetes cluster and reconcile workloads from Git using GitRepository and Kustomization resources.
Blueprints8
Physical Servers to Kubernetes Blueprint
Modernize applications running on bare-metal physical servers into containers orchestrated by Kubernetes, with phased discovery and re-platforming.
Self-Managed Kubernetes to Amazon EKS Blueprint
Migrate a self-managed (kubeadm) Kubernetes cluster to Amazon EKS, offloading control-plane operations while preserving workloads and GitOps.
Self-Managed Kubernetes to Google GKE Blueprint
Migrate a self-managed Kubernetes cluster to Google Kubernetes Engine, optionally Autopilot, to offload node and control-plane operations.
Cloud Foundry to Kubernetes Blueprint
Migrate applications from a Cloud Foundry PaaS to Kubernetes, converting buildpacks and manifests into container images and declarative deployments.
On-Prem VMs to GKE with Migrate to Containers Blueprint
Modernize on-premises VMs directly into containers on Google GKE using Migrate to Containers, skipping a separate VM rehosting step.
Manual Deployments to Argo CD GitOps Blueprint
Replace manual kubectl and script-based deploys with Argo CD GitOps so Git is the single source of truth for Kubernetes state.
Manual Deployments to Flux GitOps Blueprint
Adopt Flux CD to reconcile Kubernetes clusters from Git, replacing manual deploys with declarative, pull-based GitOps and automated image updates.
Self-Managed CI to Internal Developer Platform Blueprint
Evolve fragmented self-managed CI/CD into an internal developer platform with golden paths, self-service, and a service catalog.
Products2
Reference Architectures5
EKS Production Container Platform
A hardened, multi-account Amazon EKS platform for running production microservices with GitOps delivery and full observability.
Blue-Green Deployments on Kubernetes
A Kubernetes delivery architecture using blue-green and progressive rollouts to ship changes with instant rollback and zero downtime.
GKE Autopilot Application Platform
A managed GKE Autopilot platform on GCP that runs containers without node operations, with workload identity and integrated observability.
Multi-Cloud Portable Container Platform
A portable Kubernetes platform deployed identically across AWS, Azure, and GCP using GitOps and infrastructure as code to avoid lock-in.
End-to-End MLOps Platform on Kubernetes
A reference design for a portable MLOps platform on Kubernetes covering pipelines, experiment tracking, a model registry, serving, and monitoring.
Playbooks7
Kubernetes Platform Adoption Playbook
A phased program to stand up a production-grade internal Kubernetes platform and onboard application teams onto golden paths.
Hybrid Cloud Operating Model Playbook
A phased program to run on-premises and public cloud as one operating model with consistent identity, networking, governance, and delivery.
Infrastructure as Code Adoption Playbook
A phased program to bring an ad-hoc cloud estate under infrastructure as code with modules, pipelines, and policy enforcement.
Multi-Cloud Operating Model Playbook
A phased program to operate workloads across two or more public clouds with consistent governance, identity, and delivery while avoiding accidental lock-in.
Platform Engineering Program Playbook
A phased program to build an internal developer platform with golden paths and self-service that reduce cognitive load across product teams.
GitOps Adoption Playbook
A program to make Git the single source of truth for infrastructure and deployments using declarative, continuously reconciled delivery.
Platform Engineering and Internal Developer Platform Playbook
A program to build an internal developer platform with golden paths, self-service infrastructure, and a service catalog that reduces cognitive load.
Checklists4
Kubernetes Cluster Setup Checklist
Provision a new managed Kubernetes cluster with the networking, security, and platform add-ons teams need from day one.
GitOps Adoption Readiness Checklist
Verify the prerequisites for declarative, Git-driven Kubernetes delivery are in place before adopting GitOps.
GitOps Readiness Checklist
Verify that infrastructure and application delivery follow GitOps principles with Git as the single source of truth and automated reconciliation.
Platform Engineering & Internal Developer Platform Readiness Checklist
Assess readiness to build an internal developer platform that provides self-service, paved-path delivery for product teams.
Stacks2
GitOps Stack (ArgoCD + Terraform)
GitOps delivery: Terraform provisions infrastructure declaratively while ArgoCD continuously syncs Kubernetes application state from Git as the source of truth.
Tekton + Argo CD
A Kubernetes-native CI/CD stack pairing Tekton pipelines for in-cluster continuous integration with Argo CD for GitOps-based continuous delivery.
Comparisons2
ArgoCD vs Flux
Argo CD and Flux are the two leading GitOps continuous delivery tools for Kubernetes. Argo CD offers a rich UI; Flux is lightweight and Kubernetes-native by design.
Crossplane vs Terraform
Crossplane manages cloud infrastructure through the Kubernetes API with continuous reconciliation; Terraform uses a standalone CLI and declarative HCL with explicit plan/apply.