toolkit: ARM64 #188
-
I'm looking for a solution for reconciling the state of my cluster with Git repo. I want, literally, to provision my cluster, install some essential components, like parts of FluxCD toolkit and some secret management tool Hashicorp vault, unseal the vault, point to source-controller to the sources, and everything else should be installed automatically based on the configuration I keep in Git. I know that I can install source-controller, kustomize-controller, and helm-controller (since all of my services are using Helm) and create CRDs describing the resources I want to monitor and reconcile. The problem is that CRDs like Kustomization and HelmRelease have to be present in the cluster before the reconciliation process could start. I can potentially create one Kustomization CRD pointing to a GIT repo with all other HelmReleases needed for the rest of my services and I hope kustomize-controller will create CRDs and helm-controller reconcile them. I have to mention here that my cluster is running on arm64 SBCs and the problem with kustomize-controller is that it relies on kustomize and kubectl pulled as binaries and although kubectl can be pulled for arm64, kustomize fails to provide such option. I can easily produce multi-arch images for source-controller and helm-controller but not for kustomize-contoller. I've just started thinking if I can implement a very stupid controller which just takes all YAML files from a folder in a git repo and applies them to a Kubernetes cluster. Or maybe I'm missing some other option here? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 10 replies
-
The
We need to drop the kustomize binary and rewrite the controller parts that are shelling out to it. Fixed in fluxcd/kustomize-controller#92 |
Beta Was this translation helpful? Give feedback.
The
tk bootstrap
command does the initial setup for you.We need to drop the kustomize binary and rewrite the controller parts that are shelling out to it. Fixed in fluxcd/kustomize-controller#92