Replies: 1 comment
-
That appears to be how it was always implemented, and the javadoc does indicate that an instance will be constructed. There is a separate method for getting an existing one.
Other than some removal of deprecated methods, there hasn't been much attention paid to the SharedInformerFactory class over the years. It's probably best to just deprecate the whole thing. See #7322 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I noticed that
sharedIndexInformerFor(Class<T> apiTypeClass, long resyncPeriodInMillis)seems to create a new SharedIndexInformer instance every time, even for the same apiTypeClass.This is different from Kubernetes client-go's SharedInformerFactory, which returns a single, shared informer instance.
Question: Is this repeated creation of new informer instances intentional? If so, what is the design rationale?
Beta Was this translation helpful? Give feedback.
All reactions