kcp-dev
bug: ddsif manually manages informers
Describe the bug
Today, we manually manage the creation and lifecycle of informers in the DDSIF implementation. We've already seen bugs where this is done incorrectly, and we should just use the upstream dynamic shared informer factory. The only reason we can't do that today is that we want to be able to cancel informers when their API types are removed, and until we do the Kubernetes 1.25 rebase, we don't have a mechanism to do that.
Steps To Reproduce
.
Expected Behaviour
.
Additional Context
No response
Issues go stale after 90d of inactivity.
After a furter 30 days, they will turn rotten.
Mark the issue as fresh with /remove-lifecycle stale.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
/close
@kcp-ci-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity. Reopen the issue with
/reopen. Mark the issue as fresh with/remove-lifecycle rotten./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.