Flux All-In-One is a lightweight distribution made with Timoni for running the GitOps Toolkit controllers as a single deployable unit (Kubernetes Pod).
This distribution is optimized for running Flux on:
- Bare clusters without a CNI plugin installed
- Edge clusters with limited CPU and memory resources
- Clusters where plain HTTP communication is not allowed between pods
- Clusters with egress via HTTP/S proxies
- Serverless clusters for cost optimisation (EKS Fargate)
The versioning of this distribution follows semver with the following format:
<flux version>-<distribution release number>, e.g. 2.2.3-0.
- Distribution specifications
- Flux installation and upgrade
- Flux OCI sync configuration
- Flux Git sync configuration
- Flux multi-tenancy configuration
To deploy Flux on Kubernetes clusters, you'll be using the Timoni CLI and a Timoni Bundle file where you'll define the configuration of the Flux controllers and their settings.
Install the Timoni CLI with:
brew install stefanprodan/tap/timoniFor other installation methods, see timoni.sh.
To deploy Flux AIO on a cluster without a CNI, create a Timoni Bundle file
named flux-aio.cue with the following content:
bundle: {
apiVersion: "v1alpha1"
name: "flux-aio"
instances: {
"flux": {
module: {
url: "oci://ghcr.io/stefanprodan/modules/flux-aio"
version: "latest"
}
namespace: "flux-system"
values: {
hostNetwork: true
securityProfile: "privileged"
controllers: notification: enabled: false
}
}
}
}
Apply the bundle with:
timoni bundle apply -f flux-aio.cueNote that on clusters without kube-proxy, you'll have to add the following env vars to values:
values: env: {
"KUBERNETES_SERVICE_HOST": "<host>"
"KUBERNETES_SERVICE_PORT": "<port>"
}You can fine tune the Flux installation using various options, for more information see the installation guide.
Changes to the flux-aio.cue bundle, can be applied in dry-run mode
to see how Timoni will reconfigure Flux on the cluster:
timoni bundle apply -f flux-aio.cue --dry-run --diffTo deploy the latest version of Cilium CNI and the metrics-server cluster addon,
add the cluster-addons instance to the flux-aio.cue bundle:
bundle: {
apiVersion: "v1alpha1"
name: "flux-aio"
instances: {
// flux instance omitted for brevity
"cluster-addons": {
module: url: "oci://ghcr.io/stefanprodan/modules/flux-git-sync"
namespace: "flux-system"
values: git: {
url: "https://github.com/stefanprodan/flux-aio"
ref: "refs/heads/main"
path: "./test/cluster-addons"
}
}
}
}The above configuration, will instruct Flux to reconcile the HelmRelease manifests
from the test/cluster-addons directory.
Apply the bundle with:
timoni bundle apply -f flux-aio.cueTimoni will configure the Flux Git sync and will wait for Flux to pull the repo and deploy the cluster addons.
For more details on how to sync from private Git repositories and self-hosted Git servers, see the Git sync documentation.
If you want to use Flux AIO with a bootstrap repository layout, you'll have to add an ignore
rule for the flux-system directory and name the sync instance flux-system:
bundle: {
apiVersion: "v1alpha1"
name: "flux-aio"
instances: {
// flux instance omitted for brevity
"flux-system": {
module: url: "oci://ghcr.io/stefanprodan/modules/flux-git-sync"
namespace: "flux-system"
values: {
git: {
token: string @timoni(runtime:string:GITHUB_TOKEN)
url: "https://github.com/fluxcd/flux2-kustomize-helm-example.git"
ref: "refs/heads/main"
path: "clusters/production"
ignore: "clusters/**/flux-system/"
}
sync: wait: false
}
}
}
}The above configuration, generates the same flux-system objects (GitRepository, Secret, Kustomization)
as the flux bootstrap command.
To remove Flux from your cluster, without affecting any reconciled workloads:
flux -n flux-system uninstall
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent