https://github.com/traefik-workshops/traefik-gitops

Multi environment Traefik deployment with a GitOps Strategy
https://github.com/traefik-workshops/traefik-gitops

flux gitops ingress kubernetes kustomize load-balancer traefik

Last synced: 15 days ago
JSON representation

Multi environment Traefik deployment with a GitOps Strategy

• Host: GitHub
• URL: https://github.com/traefik-workshops/traefik-gitops
• Owner: traefik-workshops
• License: apache-2.0
• Created: 2021-11-03T10:16:58.000Z (about 3 years ago)
• Default Branch: main
• Last Pushed: 2024-05-13T14:06:33.000Z (9 months ago)
• Last Synced: 2025-01-09T12:11:36.598Z (16 days ago)
• Topics: flux, gitops, ingress, kubernetes, kustomize, load-balancer, traefik
• Language: Shell
• Homepage:
• Size: 73.2 KB
• Stars: 20
• Watchers: 5
• Forks: 7
• Open Issues: 2
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# Traefik GitOps with Flux

GitOps makes configuration management seamless by creating a single source of truth for configuration changes, so changes can be transparent, validated, and low-risk. Check out this article for step-by-step instructions on how to deploy multiple Traefik instances on two clusters with Flux using a GitOps approach.

## GitOps Principles

 - **Declarative** - the desired stated of the infrastrucutre is expressed declaratively.

 - **Versioned** and immutable - the desired state is stored in a source of truth that enforces immutability.

 - **Pulled Automatically** from a source of truth *a git repo* - the changes are pulled by Controllers and applied on a cluster.

 - **Continuously Reconciled** - the agents are continuously observing the desired state and attempt to apply the desired state.

For more details visit the tutorial entitled:  [How to Deploy Traefik using Flux and GitOps Principles](https://traefik.io/blog/deploy-traefik-proxy-using-flux-and-gitops/)