Replies: 3 comments 4 replies
-
|
flux resources are chained. Wouldn't reconciling the top level |
Beta Was this translation helpful? Give feedback.
-
|
I thought so, but it doesn't seem to work on a my HelmRelease. I have the following dependency chain:
I was able to replicate the behavior I described:
I would have expected all of these commands to have the same effect as (5). Am I doing something wrong? |
Beta Was this translation helpful? Give feedback.
-
|
Interestingly, the suspend and resume commands have an --all option, so you can e.g. force reconciliation of all kustomizations with There seems to be no --all-namespaces option for these commands. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I frequently need to delete and re-create resources while iterating on a change. For example, this is necessary to re-create PVCs that may have been initialized with incorrect data. It is also useful when iterating on a
replicasetorstatefulset, which (mostly) prohibit edits.This can leave the cluster in an inconsistent state, where some resources don't exist because they have manually been deleted (Kustomize) or uninstalled (Helm). I can force the reconciliation of individual
KustomizeandHelmReleaseresources using theflux reconcileCLI. But that requires that I know which exact flux artifacts need reconciliation.I was hoping to find a command like:
flux reconcile --allthat reconciles all resources, regardless of whether Flux thinks they have changed and/orflux reconcile -l my-label=my-label-valueto reconcile resources that have a label, regardless of whether Flux thinks they have changed and/orflux reconcile git source my-sourceto recursively reconcile all resources within the repository, regardless of whether Flux thinks they have changed.As far as I can tell, none of those exist -- but
flux reconciledoes force reconciliation of a resource if manually specify it on the command-line. I have worked around this by writing a shell script that runs a separateflux reconcilecommand for each resource that I have touched, but that is tedious and error-prone to keep that script up-to-date. How do ya'll deal with this?P.S. I am open to changing my workflow if there is a better way to iterate on changes that doesn't require solving this problem. I just haven't found one yet!
Beta Was this translation helpful? Give feedback.
All reactions