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
During the upgrade from 0.10 to 0.13 I experienced the kustomize-controller crash with a stack trace and the error fatal error: concurrent map read and map write. The controller restarts and successfully reconciles as expected, but only after re-bootstrapping a second time.
This bug does not prevent an upgrade and I am not blocked, but I wanted to report it as there might be an issue in the controller that could pop up later.
Describe the bug
During the upgrade from 0.10 to 0.13 I experienced the kustomize-controller crash with a stack trace and the error
fatal error: concurrent map read and map write
. The controller restarts and successfully reconciles as expected, but only after re-bootstrapping a second time.This bug does not prevent an upgrade and I am not blocked, but I wanted to report it as there might be an issue in the controller that could pop up later.
To Reproduce
Steps to reproduce the behaviour:
The issue was intermittent and only occurred on 2 of my 5 clusters.
Expected behavior
The kustomize-controller shouldn't crash due to this error
Additional context
Below please provide the output of the following commands:
Here are the kustomize-controller logs captured from the crash pod:
The text was updated successfully, but these errors were encountered: