Skip to content
This repository has been archived by the owner on Oct 21, 2020. It is now read-only.

Cache Node objects in external PVController library #912

Closed
verult opened this issue Aug 10, 2018 · 5 comments
Closed

Cache Node objects in external PVController library #912

verult opened this issue Aug 10, 2018 · 5 comments
Assignees
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@verult
Copy link
Contributor

verult commented Aug 10, 2018

#902 introduces topology plumbing through the library, which includes a Node get call for every volume provision operation. Since CSI depends on this library and all volumes will go through CSI in the future, we need to consider caching Node objects.

https://github.com/kubernetes-incubator/external-storage/blob/2db4446614545ef4ca87fd69ba81d24b1de390ca/lib/controller/controller.go#L1002

/assign

@wongma7
Copy link
Contributor

wongma7 commented Aug 10, 2018

would a (shared)informer be overkill or do you intend to roll your own caching?

@verult
Copy link
Contributor Author

verult commented Aug 10, 2018

Yeah it would probably just be an informer

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 25, 2019
@msau42
Copy link
Contributor

msau42 commented Apr 25, 2019

Is this issue still valid?

@verult
Copy link
Contributor Author

verult commented Apr 29, 2019

Yep, the TODO is still there though the code has been moved to lib-external-provisioner. Will move this issue there.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

5 participants