Stefan Prodan

You can exclude files using GitRepository `spec.ignore`, what's written in https://fluxcd.io/flux/faq/#can-i-use-repositories-with-plain-yamls

Let's disable it for now, no point in having something failing on all PRs with no fix in sight.

@somtochiama yes, we need to tell people to bootstrap and link to the install doc.

There are no docs because Terraform does not support custom apply logic.

@kingdonb Flux TF provider does not support patching at all. Even if you add a patch, it will not be executed at install time. Only after Flux is installed from...

> Thanks for that detail; it might be too late if the gitrepo is protected by a secret that you need to decrypt from KMS. All of this worth making...

Let me give you an example when you need to patch the Flux controllers before installation. Let's assume all your nodes are tainted, if you run `terraform apply` the Flux...

Installing Flux without a CNI is possible using a custom Deployment where all Flux controllers run inside the same pod and talk to each other over loopback. I've been experimenting...

The idea is to use this at bootstrap, setup the CNI only, then get rid of it and deploy Flux the normal way. Hence this deployment doesn't need leader election...

There are many tradeoff when running all Flux controllers in the same pod, for example you can't run them with least privileges: even if source-controller doesn't need cluster-admin you must...