-
Notifications
You must be signed in to change notification settings - Fork 181
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
Panic from kustomize / kyaml: fatal error: concurrent map writes #310
Comments
Can you please set this cmd arg |
Yep, that mitigates the issue, thanks |
This was referenced May 6, 2021
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A previously working installation of
kustomize-controller
v0.9.3 has started to panic shortly after startup, with the following backtrace:Backtrace
I can't link this to any particular commit to the repo it points at. It seems to be reliably triggered on every startup, and the
kustomize-controller
pod never becomes healthy.It looks like this is related to the following upstream bug: kubernetes-sigs/kustomize#3659 which is not yet fixed.
Does it make sense to mutex around buildKustomization to avoid this until the upstream bug is fixed?
terraform-provider-kustomization
has taken that approach as a temp fix.The text was updated successfully, but these errors were encountered: