You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Warning ReconciliationFailed 3m23s kustomize-controller postgresql/discourse/discourse-db dry-run failed: no matches for kind "postgresql" in version "acid.zalan.do/v1"
The current solutions would be to
create the resources step-by-step, splitting up normal PRs to multiple:
install postgres-operator
apply application
apply the intermediate resources by hand every time
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: