specificInformersMap Get may accidentally return an unynced informer

[nvachhar]

If specificInformersMap is already started, a call to Get that doesn't find a particular GVK will create the corresponding Informer, add it to the map, and then wait for it to sync. Therefore the caller will get a synced Informer. However, if there is a concurrent caller to Get for the same GVK, it will find the Informer in the map and return it without waiting for it to sync. Therefore the concurrent caller will get an unsynced informer.

[nvachhar]

I forgot to mention, I have a patch to fix the problem. Just posting the issue to ensure others agree with the problem's existence.

[DirectXMan12]

go ahead and submit the PR to fix it, please

/kind bug

[adohe-zz]

/close

[k8s-ci-robot]

@adohe: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.