How to Organise a Flux CD Monorepo

Do you already have more than one or two clusters and realize it's time to use some IaC solution? Have you heard something about Flux, but don't know how to use it?

Or have you already set up several clusters, each in its own repository, and everything seems to be working fine, but the update process no longer seems convenient? I think you should try the monorepo approach.

I will talk about our organization of such a monorepo, which we have been building at Altenar for more than 3 years, how such a structure helps us, and what annoys us about it. How to properly package an application for reuse and create templates for network policies, and so on.

Technologies: K8s, Flux CD, IaC.

Will be useful to infrastructure engineers and DevOps of different profiles.