Workloads
What runs on the folly and offsite Kubernetes clusters, the files that list it, and the workloads that have their own page.
A workload is an app or controller that Flux runs on one of the two Kubernetes clusters. Git holds the full list for each cluster.
offsite runs the public and upload-heavy workloads, because folly's internet link has little upload capacity. folly runs the household, media and lab workloads, and the ones that need riptide's GPU.
Where it lives#
| File or directory | What it lists |
|---|---|
clusters/<site>/apps/kustomization.yaml | The apps in the apps Flux Kustomization. A commented-out line does not run. |
clusters/<site>/flux-system/ | The other Flux Kustomizations of the cluster, such as networking, monitoring, arc-runners and oauth2-proxy |
clusters/base/flux-system/ | The shared controllers in clusters/base/platform/, which both clusters run |
clusters/base/apps/ | Apps that both clusters include by path |
A .yaml file in clusters/folly/apps/ next to a directory of the same name is a Flux Kustomization that applies that directory.
Inspect workloads#
| Question | Command |
|---|---|
| Which Flux Kustomizations are live? | flux --context <site> get kustomizations -A |
| Which Helm releases are live? | flux --context <site> get helmreleases -A |
| Which objects does a directory produce? | kubectl kustomize <path> |
| Does each directory render? | mise run k8s:render-apps |
The render check reports errors. It does not print the objects.
Workloads with a page#
| Workload | Cluster | Page |
|---|---|---|
| kthx quick-site server | offsite | Quick sites |
| kthx built-app engine | offsite. It deploys built apps to both clusters. | Built apps |
| clankerbanker | offsite, as a kthx built app | clankerbanker |
| Rowbutt | offsite | Rowbutt |
| Weather Hub | offsite | Weather Hub |
| PBX | both | PBX |
| Smiirl counter | folly | Smiirl counter |
| Tidbyt apps | folly | Tidbyt apps |
| Flame Boss exporter | folly | Flame Boss exporter |
| netbench | folly, with iperf3 on both | netbench |
| Monitoring | both | Observability |
| Atlantis | offsite | OpenTofu and Atlantis |
| GitHub Actions runners | both | Build and release |
| OpenBao | folly | Secrets |
| Postgres databases | both | Operate Postgres |
Argo CD runs on folly from clusters/folly/apps/argo/. Git declares no Argo Application. The kthx engine creates Applications in argo for a folly kubernetes Target that delivers through Argo (Built apps).
Related#
Linked from 1
- KubernetesThe folly and offsite Kubernetes clusters, how Flux applies clusters/ from git, and the sandbox runtimes and storage the clusters offer.