You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to kubernetes-sig-storage
Hello,
I was wondering whether the K8s storage framework and API (i.e. Storage classes, PVCs, PVs, etc...) has been designed from scratch, or if instead it was inspired by prior work (either in industry or academia).
In the latter case, what were the predecessors? Are there scientific papers/blog posts about them?
Thanks,
Matteo.
Ben Swartzlander
unread,
Nov 26, 2023, 10:22:30 PM11/26/23
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to kubernetes-...@googlegroups.com
The current storage APIs evolved organically. Originally the system only
supported statically provisioned volumes, and dynamic provisioning was
added later. CSI was added after that. Knowing what we know now, we
probably would have designed things a bit differently if we got a chance
to do it over.
A large number of people have contributed to SIG storage over the years
and they all bring their own experiences. I don't believe there was ever
an intention to directly copy another API or implement a design from any
papers, but certainly many of the contributors have worked on other
systems and brought lessons to the design process of what works and what
doesn't work.