From f767dde0cc33db0644b420533544a360d82d055a Mon Sep 17 00:00:00 2001 From: Devin Buhl Date: Fri, 22 Dec 2023 20:55:01 -0500 Subject: [PATCH] chore: Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index f7b875ba3fdfd..b1c9b3b0a752d 100644 --- a/README.md +++ b/README.md @@ -70,7 +70,7 @@ My cluster is [k3s](https://k3s.io/) provisioned overtop bare-metal Debian using [Flux](https://github.com/fluxcd/flux2) watches the clusters in my [kubernetes](./kubernetes/) folder (see Directories below) and makes the changes to my clusters based on the state of my Git repository. -The way Flux works for me here is it will recursively search the `kubernetes/${cluster}/apps` folder until it finds the most top level `kustomization.yaml` per directory and then apply all the resources listed in it. That aforementioned `kustomization.yaml` will generally only have a namespace resource and one or many Flux kustomizations (`ks.yaml`). Those Flux kustomizations will generally have a `HelmRelease` or other resources related to the application underneath it which will be applied. +The way Flux works for me here is it will recursively search the `kubernetes/${cluster}/apps` folder until it finds the most top level `kustomization.yaml` per directory and then apply all the resources listed in it. That aforementioned `kustomization.yaml` will generally only have a namespace resource and one or many Flux kustomizations (`ks.yaml`). Under the control of those Flux kustomizations there will be a `HelmRelease` or other resources related to the application which will be applied. [Renovate](https://github.com/renovatebot/renovate) watches my **entire** repository looking for dependency updates, when they are found a PR is automatically created. When some PRs are merged Flux applies the changes to my cluster.