Open cwrau opened 3 weeks ago
There is spec.dependsOn
made for this, see here how to use it: https://github.com/fluxcd/flux2-kustomize-helm-example?tab=readme-ov-file#infrastructure
There is
spec.dependsOn
made for this
But what if I don't have anything that can use depensOn
or the dependee can't be depended upon?
Imagine the following scenario;
application.yaml
with plain k8s resources, including a custom postgresql
resourceoperator.yaml
with a flux HelmRelease with the operatorthat won't work with the dependsOn
(or need the solution below)
, see here how to use it: fluxcd/flux2-kustomize-helm-example#infrastructure
And in this example, I'd need to have multiple kustomizations, which,, in my use-case,, really only serve the purpose for ordering
Often one installs dependent configuration at the same time, think postgres-operator and the application with the postgresql.
With flux this is, currently, not possible, as the kustomize-controller fails with
The current solutions would be to
Both of these solutions have the disadvantage to not work with a full recovery with an existing repo.
In my opinion, an option with
partialApply: true
would be amazing, which would just apply everything that's possible and ignore what's not working, but still failing at the end.And during the next reconciliation trying again, which,, in time,, would result in a complete working cluster.