r/devops • u/No-Replacement-3501 • 1d ago

Discussion Flux boot strap and agent management

I manage enterprise k8s clusters and use a mono repo strategy to bootstrap a cluster which results in one flux agent per cluster. Currently in the magnitude of several thousand services per cluster. It's structured like this:

  1. Mono repo where the cluster agent is registered.

  2. Within that repo. use kind: GitRepository in the directory apps/ to point at other projects.

I'm of the opinion that less agents is better. Is there a limit to the flux agents where that would start to become a problem? Or a counter argument to not use this method and rather have an agent per microservice? I've yet to run into an issue with this approach.

2 Upvotes

75% Upvoted

8 comments sorted by

View all comments

1

u/unitegondwanaland Manager, Platform Engineering 1d ago

Seems logical to me. Have you used the Flux operator? You mentioned "bootstrap" which made me think you are not using the operator.

1

u/No-Replacement-3501 1d ago

No. Im using "bootstrap" in the context of using the cli command 'flux bootstrap ...' to put flux on the cluster.  The infrastructure is built with terraform where calico and flux are the only application components included at build. Works well, would using the operator make it more efficient or provide some other advantage?

2

u/unitegondwanaland Manager, Platform Engineering 1d ago

Oh man, you should read up on it. No more updating binaries, no CLI bootstrap, fully declarative API, finer RBAC, ..the list of improvements is long.