🐛 Instantiate kube index informers by default #54
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Our wrapper overrides the
NewInformer
method in order to create scopable cluster-aware shared index informers. But in normal, non-kcp mode we don't want that and instead instantiate a normal kube shared index informers, with traditionalnamespace/name
keys without cluster name.This matter when running a controller against one single workspace. Every object will have a
kcp.io/cluster
annotation, but we don't want it as part of the informer key.