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
{{ message }}
This repository was archived by the owner on Apr 4, 2023. It is now read-only.
We should update this to use a custom generated SharedInformerFactory that supports namespaced resources, and simplify all of this informer handling logic for good.
The text was updated successfully, but these errors were encountered:
Automatic merge from submit-queue.
Use filtered SharedInformerFactories in controller context
**What this PR does / why we need it**:
Switches to using the new filtered SharedInformerFactories as part of kubernetes/kubernetes#54660
**Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #
fixes#69
**Special notes for your reviewer**:
Don't merge until #79 has been merged
**Release note**:
```release-note
NONE
```
/assign @wallrj
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Right now we construct informers through a really horrible and non-type safe SharedInformerFactory, in order to support running in a single namespace (see: https://github.com/jetstack/navigator/blob/master/pkg/controllers/elasticsearch/elasticsearch.go#L311)
We should update this to use a custom generated SharedInformerFactory that supports namespaced resources, and simplify all of this informer handling logic for good.
The text was updated successfully, but these errors were encountered: