Flux Multi-cluster Architecture

[stefanprodan]

Check out my blog post on Flux multi-cluster architecture to learn the differences between running Flux in a distributed manner vs centralised hub-spoke mode. https://fluxcd.control-plane.io/guides/flux-architecture/

TL;DR

Running Flux in the standalone mode offers a higher degree of security and autonomy for the clusters at the expense of operational overhead when it comes to bootstrapping and monitoring the Flux instances.

The hub and spoke mode reduces the operational and maintenance overhead by centralizing the GitOps continuous delivery tooling on a single Kubernetes cluster, but introduces a single point of failure and networking complexity that can be challenging from a security perspective.

[matofeder]

Hi @stefanprodan

Does the repository structure in flux2-hub-spoke-example offer any significant advantages?
Structure from example repository:

- clusters/
     production/
     staging/  
- deploy/
     apps/
     ...
 - hub/
     flux-system/
     production.yaml
     staging.yaml

I’m considering using the following alternative:

- deploy/
     apps/
     ...
 - hub/
     flux-system/
     production/
         production.yaml
     staging/
         staging.yaml

Beyond the general principle that "flat is better than nested," are there any potential concerns I should reassess?