github/awesome-kubernetes
1
0
Fork 0
mirror of https://github.com/nubenetes/awesome-kubernetes.git synced 2026-07-12 18:00:37 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
19b7b44e2077259c19659b1c82b5f79acf6fa236
awesome-kubernetes/v2-docs/gitops.md
Nubenetes Bot 19b7b44e20 feat(v2): restore in-page search/tag filter & drop redundant Markdown TOC 
Fix: the per-page resource search box with maturity tag-pills stopped
appearing after navigation.instant was enabled (DOMContentLoaded fires only
on first SPA load). Reworked v2_filter.js to init via Material's document$
observable with a DOMContentLoaded fallback, guard double-injection, bind the
clickable-tag delegation once, and add a no-results state. Cache-bust ?v=2.9.12.

Change: removed the duplicated Markdown "## Table of Contents" from all 156 V2
content pages and from v2_optimizer.py — it forced hundreds of links of scroll
on large pages. Replaced by Material's native sticky "On this page" TOC
(removed toc.integrate, added toc.follow). tags.md keeps its TOC (it is an index).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-19 18:49:15 +02:00

127 lines
17 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# GitOps
!!! tip "Nubenetes V2 Elite Portal"
You are browsing the AI-Curated V2 Elite Edition. Looking for the exhaustive list of references? Check out the [**V1 Historical Archive**](/v1/gitops/).
!!! info "Architectural Context"
Detailed reference for GitOps in the context of Engineering Pipeline.
## API Management
### GitOps (1)
#### Declarative APIs
- **(2022)** [thenewstack.io: Can You GitOps Your APIs?](https://thenewstack.io/can-you-gitops-your-apis) <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Examines extending declarative GitOps paradigms to microservice API configurations and gateway endpoints. Demonstrates the technical practicality of driving schema changes, routing configurations, and security policies dynamically via version-controlled API blueprints rather than using manual management consoles.
## Application Delivery
### Continuous Deployment
#### GitOps (2)
##### Business Value
- **(2020)** [blog.container-solutions.com: 11 Reasons for Adopting GitOps](https://blog.container-solutions.com/why-adopt-gitops) <span class='md-tag md-tag--warning'>[NONE CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Presents key reasons for adopting GitOps, focusing on deployment reliability, audit compliance, developer velocity, and cluster disaster recovery. It translates complex technical capabilities into clear business metrics like release frequency and overall uptime. This helps engineering leaders justify platform modernization efforts.
##### DevOps Culture
- **(2021)** [atlassian.com: Is GitOps the next big thing in DevOps?](https://www.atlassian.com/git/tutorials/gitops) <span class='md-tag md-tag--warning'>[NONE CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Examines GitOps from a broader DevOps perspective, showing how Git-based review approvals improve developer velocity and security auditing. It illustrates how using pull requests for infrastructure configuration builds collaboration between engineering teams. This cultural alignment is key to successful modern cloud adoptions.
- **(2021)** [thenewstack.io: What Is GitOps and Why It Might Be The Next Big Thing for DevOps](https://thenewstack.io/software-development) <span class='md-tag md-tag--warning'>[NONE CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Discusses the industry-wide evolution from manual deployment scripting toward robust declarative GitOps controllers. By abstracting execution environments inside the cluster, security risks and operational overhead are dramatically reduced. It highlights how GitOps enables faster onboarding of junior developers.
- **(2021)** [opensource.com: GitOps vs. DevOps: What's the difference? 🌟](https://opensource.com/article/21/3/gitops) <span class='md-tag md-tag--warning'>[NONE CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Compares traditional DevOps philosophies with structured GitOps methodologies, illustrating how GitOps provides a concrete implementation pattern for DevOps. While DevOps represents a broad system of collaboration principles, GitOps delivers a strict, technical model for cloud-native infrastructure automation using version control.
##### Ecosystem
- **(2021)** [thenewstack.io: Understanding GitOps: The Latest Tools and Philosophies](https://thenewstack.io/understanding-gitops-the-latest-tools-and-philosophies) <span class='md-tag md-tag--warning'>[NONE CONTENT]</span> <span class='md-tag md-tag--warning'>[EMERGING]</span> — Synthesizes emerging GitOps technologies and delivery paradigms. It focuses on how modern sync engines handle connectivity losses in hybrid environments and manage multi-tenant boundaries. It serves as a great tool for architects planning future-proof application delivery frameworks.
##### Foundations
- **(2020)** [weave.works: Guide to GitOps](https://www.weave.works/technologies/gitops) <span class='md-tag md-tag--warning'>[NONE CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A foundational guide to GitOps concepts as originally defined and structured by Weaveworks. While Weaveworks pioneered these patterns and early delivery agents (Curator Insight), corporate closures shifted direct tooling maintenance to broader CNCF communities (Live Grounding). The design principles remain core to modern cloud-native CD.
##### Implementation
- **(2021)** [itnext.io: Continuous GitOps, the way to do DevOps in Kubernetes 🌟](https://itnext.io/continuous-gitops-the-way-to-do-devops-in-kubernetes-896b0ea1d0fb) <span class='md-tag md-tag--warning'>[YAML CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A duplicate entry detailing continuous GitOps deployment processes and pipeline architectures. It highlights methods to trace and mitigate configuration drift in large-scale microservice deployments. Organizing repositories with structured directory configurations is key to managing complex, multi-environment cluster setups.
- **(2021)** [sufle.io: Adopting GitOps for Enhanced Operations](https://www.sufle.io/blog/adopting-gitops-for-enhanced-operations) <span class='md-tag md-tag--warning'>[NONE CONTENT]</span> <span class='md-tag md-tag--critical'>[LEGACY]</span> — A migration guide helping organizations transition from legacy imperative deployment workflows to modern, git-driven operational pipelines. By defining the target state declaratively, incident management and disaster recovery speeds are greatly improved. This shift reduces Mean Time to Resolution (MTTR) under stressful outage conditions.
##### Source Code
- **(2026)** [github.com/topics/gitops 🌟](https://github.com/topics/gitops) <span class='md-tag md-tag--warning'>[GO CONTENT]</span> <span class='md-tag md-tag--warning'>[EMERGING]</span> — A dynamically aggregated index of GitOps-related source code repositories and tooling hosted on GitHub. It connects engineers to reconciliation agents, helper plugins, and template engines. It serves as a great source for discovering emerging, community-driven deployment automation utilities.
##### Standards
- **(2021)** [OpenGitOps.dev 🌟](https://opengitops.dev) <span class='md-tag md-tag--warning'>[NONE CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — The home of the CNCF GitOps Working Group, detailing the official OpenGitOps standards. It defines the formal criteria required for GitOps systems: declarative states, versioned storage, pull-based delivery, and continuous reconciliation loop synchronization. Adhering to these principles ensures consistency, auditability, and robust security in automated delivery chains.
### Infrastructure as Code
#### Patterns
- **(2021)** [itnext.io: Principles, Patterns, and Practices for Effective Infrastructure as Code](https://itnext.io/principles-patterns-and-practices-for-effective-infrastructure-as-code-e5f7bbe13df1) <span class='md-tag md-tag--warning'>[TERRAFORM CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Maps out foundational engineering principles applied to Infrastructure as Code (IaC), including modular design, idempotency, and automated testing. These practices ensure underlying infrastructure layouts remain stable and predictable. This structural guidance is crucial to building scaling pipelines that feed into GitOps controllers.
## CICD
### GitOps (3)
#### Deployment Strategies
- **(2021)** [about.gitlab.com: 3 Ways to approach GitOps 🌟](https://about.gitlab.com/blog/gitops-done-3-ways) <span class='md-tag md-tag--warning'>[YAML CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> <span class='md-tag md-tag--secondary'>[GUIDE]</span> — A structured analysis comparing three common approaches to implementing GitOps. Contrasts pull-based versus push-based agent configurations, discussing security considerations, cluster scaling restrictions, and auditability trade-offs.
#### FluxCD
- **(2025)** [Flux. The GitOps operator for Kubernetes](https://nubenetes.com/flux/) <span class='md-tag md-tag--warning'>[GO CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — The main technical documentation and resources for Flux, the CNCF-graduated continuous delivery tool for Kubernetes. Analyzes multi-tenancy configurations, automated image update policies, and source controller optimizations that make Flux a core component of modern GitOps workflows.
#### Kustomize Manifests
- **(2025)** [Kustomize - Template-Free Kubernetes Configuration Customization](https://nubenetes.com/kustomize/) <span class='md-tag md-tag--warning'>[GO CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Technical reference for Kustomize, the template-free engine used to manage Kubernetes configurations. Details declarative base and overlay architectures, allowing developers to manage configurations for different environments (dev, staging, prod) without using complex Helm template structures.
## Continuous Delivery
### GitOps (4)
#### Kubernetes Native
- **(2022)** [piotrminkowski.com: Continuous Development on Kubernetes with GitOps Approach 🌟](https://piotrminkowski.com/2022/06/06/continuous-development-on-kubernetes-with-gitops-approach) <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Presents a real-world developer workflow utilizing GitOps frameworks during local and remote microservice development. Details how to tightly couple development loops with rapid Git-based deployments to maintain real-time sync with cloud-native testbeds.
#### Telco and Edge
- **(2021)** [weave.works: The world’s largest telcos are now embracing GitOps. Deutsche Telekom explains why](https://www.weave.works/blog/deutsche-telekom-explain-why-they-chose-gitops-for-5g) <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Case study analyzing how major telecommunications networks (e.g., Deutsche Telekom) apply GitOps workflows to govern large-scale 5G infrastructure. Curator Insight validates complex hybrid deployments, while Live Grounding proves the absolute necessity of Git-driven edge management to ensure consistent performance over thousands of remote kubernetes endpoints.
#### Testing Environments
- **(2021)** [==github.com/cloudogu/gitops-playground#example-applications==](https://github.com/cloudogu/gitops-playground) <span class='md-tag md-tag--info'>⭐ 266</span> <svg class="v2-sparkline" width="50" height="15" viewBox="0 0 50 15" style="vertical-align: middle; display: inline-block; margin-left: 6px;" title="Activity Trend"><defs><linearGradient id="spark-grad-0faf32a2" x1="0" y1="0" x2="1" y2="0"><stop offset="0%" stop-color="rgba(34, 211, 238, 0.2)" /><stop offset="100%" stop-color="var(--md-accent-fg-color)" /></linearGradient></defs><path class="v2-sparkline-path" d="M 0 9 L 10 3 L 20 13 L 30 3 L 40 13 L 50 4" fill="none" stroke="url(#spark-grad-0faf32a2)" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round" /><circle cx="50" cy="4" r="2" fill="var(--md-accent-fg-color)" /></svg> <span class='md-tag md-tag--warning'>[SHELL CONTENT]</span> 🌟🌟🌟🌟🌟 <span class='md-tag md-tag--success'>[DE FACTO STANDARD]</span> — A fully configured local testing playground that showcases multi-tool GitOps pipelines. Includes pre-wired sample apps to help developers analyze live sync processes, drift reconciliation, and integration dynamics using ArgoCD and Flux.
### Progressive Delivery
#### GitOps Integration
- **(2023)** [opensourceforu.com: Embracing Progressive Delivery In Kubernetes With GitOps](https://www.opensourceforu.com/2023/10/embracing-progressive-delivery-in-kubernetes-with-gitops) <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Detailing structural implementations of progressive delivery, such as automated canaries, A/B testing, and blue-green rollouts, working in tandem with GitOps tools (like Flagger or Argo Rollouts) to control application lifecycle safety dynamically.
## GitOps (5)
### Methodology
#### Developer Platforms
- **(2021)** [shipa.io: GitOps meets AppOps](https://shipa.io/gitops-meets-appops) <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Evaluates how AppOps layers complement GitOps by shielding developers from Kubernetes YAML complexities. Highlights platform engineering concepts, allowing devs to focus on app metadata while the platform manages lower-level configurations.
## Networking
### Ingress and Gateway
#### Automation
- **(2021)** [github.com/stakater/Xposer](https://github.com/stakater/Xposer) <span class='md-tag md-tag--info'>⭐ 32</span> <svg class="v2-sparkline" width="50" height="15" viewBox="0 0 50 15" style="vertical-align: middle; display: inline-block; margin-left: 6px;" title="Activity Trend"><defs><linearGradient id="spark-grad-445d2e7c" x1="0" y1="0" x2="1" y2="0"><stop offset="0%" stop-color="rgba(34, 211, 238, 0.2)" /><stop offset="100%" stop-color="var(--md-accent-fg-color)" /></linearGradient></defs><path class="v2-sparkline-path" d="M 0 7 L 10 3 L 20 10 L 30 11 L 40 13 L 50 2" fill="none" stroke="url(#spark-grad-445d2e7c)" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round" /><circle cx="50" cy="2" r="2" fill="var(--md-accent-fg-color)" /></svg> <span class='md-tag md-tag--warning'>[GO CONTENT]</span> 🌟 <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A lightweight automation operator designed to monitor services and dynamically generate DNS-mapped Ingress resources to reduce manual administrative overhead.
### Service Mesh
#### eBPF vs Proxy
- **(2021)** [solo.io: Exploring Cilium Layer 7 Capabilities Compared to Istio](https://www.solo.io/blog) <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — Architectural analysis contrasting Cilium's kernel-level L7 eBPF traffic management with Istio's user-space Envoy proxy routing, comparing performance and complexity trade-offs.
## Platform Architecture
### GitOps (6)
#### Modern Pipelines
- **(2020)** [openshift.com: From Code to Production with GitOps, Tekton and ArgoCD 🌟](https://www.redhat.com/en/blog/from-code-to-production-with-gitops) <span class='md-tag md-tag--warning'>[YAML CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> <span class='md-tag md-tag--success'>[DE FACTO STANDARD]</span> <span class='md-tag md-tag--success'>[ENTERPRISE-STABLE]</span> — Introduces robust continuous delivery architectures utilizing Tekton for image construction and Argo CD for GitOps-based state syncs. Serves as the primary operational blueprint for enterprise microservice platforms in 2026.
## Platform Engineering
### GitOps and Deployment
#### Flux Ecosystem
- **(2021)** [==github: Flux==](https://github.com/fluxcd/flux) <span class='md-tag md-tag--info'>⭐ 6861</span> <svg class="v2-sparkline" width="50" height="15" viewBox="0 0 50 15" style="vertical-align: middle; display: inline-block; margin-left: 6px;" title="Activity Trend"><defs><linearGradient id="spark-grad-520daebf" x1="0" y1="0" x2="1" y2="0"><stop offset="0%" stop-color="rgba(34, 211, 238, 0.2)" /><stop offset="100%" stop-color="var(--md-accent-fg-color)" /></linearGradient></defs><path class="v2-sparkline-path" d="M 0 2 L 10 13 L 20 2 L 30 12 L 40 6 L 50 5" fill="none" stroke="url(#spark-grad-520daebf)" stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round" /><circle cx="50" cy="5" r="2" fill="var(--md-accent-fg-color)" /></svg> <span class='md-tag md-tag--warning'>[GO CONTENT]</span> 🌟🌟🌟🌟🌟 <span class='md-tag md-tag--success'>[DE FACTO STANDARD]</span> <span class='md-tag md-tag--critical'>[LEGACY]</span> — The deprecated and archived GitHub repository for the original Flux v1 GitOps engine. Completely succeeded by the microservice-driven, decoupled Flux v2 architecture.
- **(2021)** [itnext.io: Managing Kubernetes Secrets Securely with GitOps (SOPS + AWS KMS + Flux)](https://itnext.io/managing-kubernetes-secrets-securely-with-gitops-b8174b4f4d30) <span class='md-tag md-tag--warning'>[YAML CONTENT]</span> <span class='md-tag md-tag--info'>[COMMUNITY-TOOL]</span> — A crucial guide explaining how to securely manage encrypted Kubernetes Secrets in public Git repositories using Mozilla SOPS, AWS KMS, and the Flux source/kustomize decryption drivers.
### Multi-Cluster Routing
#### Fleet Orchestration
- **(2020)** [==open-cluster-management.io==](https://open-cluster-management.io) <span class='md-tag md-tag--warning'>[GO CONTENT]</span> <span class='md-tag md-tag--critical'>[ADVANCED LEVEL]</span> 🌟🌟🌟🌟🌟 <span class='md-tag md-tag--success'>[DE FACTO STANDARD]</span> — Open Cluster Management (OCM) is a modular, extensible CNCF project designed to orchestrate fleets of Kubernetes clusters at scale. It defines standardized API abstractions for cluster registration, application deployment policies, and compliance management.
---
💡 **Explore Related:** [Jenkins](./jenkins.md) | [Tekton](./tekton.md) | [Argo](./argo.md)
🔗 **See Also:** [About](./about.md) | [Postman](./postman.md)
Reference in New Issue View Git Blame Copy Permalink