-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Concurrency issues with flux build without kustomization.yaml #483
Comments
Yeah, i've seen Does this mean that both kustomizations |
My setup is using the same setup as the but for the
which looks like this:
and the
|
Ah! So effectively what is happening then is the A workaround can be to use the I see two potential issues to follow on here:
Also related is #360 which talks about more issues with external git repos |
I can confirm if I completely remove the Trying to use the sources argument didn't seems to work (it's still flaky), the
|
I made a PR to attempt to add a repo to reproduce the --sources issue but it seems to be filtering for me. Perhaps you can see if i'm missing something? #487 Perhaps try with Does |
Yes the PR looks correct, it's the same as my setup. Filtering with
vs without filtering
Also checked
Checking the executed
vs for diff
it will still try to process the
Yes |
Added concurrency limits by kustomization path in aee9331 |
I was able to test it and it seems to be working fine now with the fix, thank you! |
With version v4 I noticed that the
allenporter/flux-local/action/diff
action is started to fail.In the error there are errors regarding the generation of the
kustomization.yaml
e.g.:As the error occurs in different places for each run my guess is that it's related to flux build generating the
kustomization.yaml
file but as multiple build commands are run parallel they will collide on the same file.To verify I changed the concurrency level to 1 in here: https://github.com/allenporter/flux-local/blob/main/flux_local/command.py#L17
and it seems to "solved" the issue.
The text was updated successfully, but these errors were encountered: