Implement the patches for Flux All-In-One installation

[kvaps]

Is your feature request related to a problem ?

There was a discussion on how to install FluxCD without CNI
fluxcd/flux2#3070

Right now there is no standard and convenient way for doing this.

Describe the solution you'd like.

Add additional option to values.yaml

# -- Implement the patches for Flux All-In-One installation as a single deployable unit (Kubernetes Pod).
# See https://github.com/fluxcd/flux2/discussions/3070
aio: false

Describe alternatives you've considered.

There are certain projects for solving this issue:

• https://github.com/stefanprodan/flux-aio
• https://github.com/maxpain/flux-without-cni/blob/main/kustomization.yaml

I'd like to have a common way to generate a ready manifests to apply.

Additional context.

I can prepare the PR for this feature, but let's first discuss if it is needed and how it should be implemented

cc @stefanprodan @maxpain
I would like to hear your opinion as well

[maxpain]

Yes it's a really must have feature.

I deploy Cilium CNI using Flux on a lot of clusters.

[gecube]

@maxpain won't FluxCD operator solve this issue? Anyway, I totally agree, that this option is a must. Particularly I want to highlight that it is not enough to put all fluxCD pods into host network, but also one needs to deal with DNS (as CoreDNS is not working w/o CNI)