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
Hello all. I have my entire cluster infra deployed via Flux, it works great, and I use dependsOn to define dependencies and create an order in which infra services come up.
However, as the infra has grown, my development cycles have gotten longer due to those dependencies. When a new commit comes in, Flux reconciles each dependency one at a time, even if I only changed a single line in something that happens all the way at the end.
As a short-term work-around, I just remove the dependencies for the one kustomization I'm working on, and then restore them when I'm done.
Is there any way flux can quickly skip to the only diff'ed kustomization instead of going through everything one at a time?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello all. I have my entire cluster infra deployed via Flux, it works great, and I use dependsOn to define dependencies and create an order in which infra services come up.
However, as the infra has grown, my development cycles have gotten longer due to those dependencies. When a new commit comes in, Flux reconciles each dependency one at a time, even if I only changed a single line in something that happens all the way at the end.
As a short-term work-around, I just remove the dependencies for the one kustomization I'm working on, and then restore them when I'm done.
Is there any way flux can quickly skip to the only diff'ed kustomization instead of going through everything one at a time?
Beta Was this translation helpful? Give feedback.
All reactions