If ControllerResourceEventCource
not initialized firtst can cause issues with indexing and secondary to primary mapping
#1238
Labels
kind/bug
Categorizes issue or PR as related to a bug.
Uh oh!
There was an error while loading. Please reload this page.
Source code from Flink operator. Such cases if the controller ES is not initialized first it will mean that the informer's SecondaryToPrimaryMapper won't find resource in the primary index. This is quite natural setup, so makes sense to in general to init ControllerResourceEventSource as first, so the index is filled when other event source are started, so their index is filled also correctly.
The text was updated successfully, but these errors were encountered: