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
An unrelated test run encountered a data race when building clusters for separate tests. It's unclear if this is a race on our part or a bug in the kustomize library. The code on our side doesn't seem an obvious culprit. The exit point from our code is the kustomize invocation, and our only inputs to k.Run() are a fresh random tempdir generated in GetKustomizedManifest() and a kustomize library function that returns a fresh empty object. krusty.MakeKustomizer() (the k receiver) also returns a fresh empty object.
The actual race is buried somewhere in the bowels of kustomize code, so without an obvious shared input value from us it looks like a bug on their end. Haven't explored the kustomize code fully to try and explain it. I did not find any existing issue on https://github.com/kubernetes-sigs/kustomize/issues
I've quickly glanced through code and kustomize issue and also couldn't find a related one so I've created this one to track this problem: kubernetes-sigs/kustomize#4824
An unrelated test run encountered a data race when building clusters for separate tests. It's unclear if this is a race on our part or a bug in the kustomize library. The code on our side doesn't seem an obvious culprit. The exit point from our code is the kustomize invocation, and our only inputs to
k.Run()
are a fresh random tempdir generated inGetKustomizedManifest()
and a kustomize library function that returns a fresh empty object.krusty.MakeKustomizer()
(thek
receiver) also returns a fresh empty object.The actual race is buried somewhere in the bowels of kustomize code, so without an obvious shared input value from us it looks like a bug on their end. Haven't explored the kustomize code fully to try and explain it. I did not find any existing issue on https://github.com/kubernetes-sigs/kustomize/issues
The text was updated successfully, but these errors were encountered: