[HN Gopher] Show HN: Searchable Kubernetes CSI provider listing
___________________________________________________________________
Show HN: Searchable Kubernetes CSI provider listing
Author : noctarius
Score : 19 points
Date : 2024-06-16 19:05 UTC (3 hours ago)
(HTM) web link (storageclass.info)
(TXT) w3m dump (storageclass.info)
| patrakov wrote:
| Some search terms (try "iscsi") break the site due to JS errors:
| Uncaught TypeError: e.description is undefined e
| https://storageclass.info/storageclasses/:6
| filterStoragesClasses https://storageclass.info/storageclasses/:6
| oninput https://storageclass.info/storageclasses/:6
|
| 2 storageclasses:6:204943 e
| https://storageclass.info/storageclasses/:6 filter self-
| hosted:195 filterStoragesClasses
| https://storageclass.info/storageclasses/:6 oninput
| https://storageclass.info/storageclasses/:6
|
| Additionally, https://plausible.io/js/script.js is blocked by
| adblockers, and the search breaks completely then.
| noctarius wrote:
| Uh! Thanks for mentioning. Also wasn't aware that plausible is
| blocked, thanks for the hint, even though I wonder why it
| breaks the search. I'll figure it out. Thanks again.
| __turbobrew__ wrote:
| Does anyone have good experiences with a replicated storage CSI
| which can run on commodity hardware?
|
| I tried out OpenEBS Replicated -- and it is promising -- but it
| doesn't really seem mature yet. Im a bit scared to put production
| critical data into it.
| candiddevmike wrote:
| What problem are you trying to solve with replicated storage?
|
| A lot of times, finding a solution further up the stack or
| settling for backups ends up being more robust and reliable.
| Many folks have been burnt by all the fun failure scenarios of
| replicated filesystems.
| __turbobrew__ wrote:
| I build a platform which hosts a few thousand services and
| tens of thousands of nodes. Currently, those services need to
| each internally manage replicating data and need to be aware
| of failure domains (host, rack, data center).
|
| What I would like to do is develop a system where
| applications just need to request replicated volumes which
| span a specific failure domain and push that logic down to
| the platform.
| noctarius wrote:
| Guess you want a block storage?
| erulabs wrote:
| My experience is that OpenEBS and Longhorn are cool and new and
| simplified, but that I would only trust my life to Rook/Ceph.
| If it's going into production, I'd say look at https://rook.io/
| - Ceph can do both block and filesystem volumes.
| __turbobrew__ wrote:
| Thanks, I will look at Rook.
| candiddevmike wrote:
| While this may be useful to some folks, it appears to be content
| marketing for https://www.simplyblock.io/, FYI.
| willcodeforfoo wrote:
| Somewhat related: can anyone recommend a simple solution to share
| each node's ephemeral disk/"emptyDir" across the cluster? Speed
| is more important than durability, this is just for a temporary
| batch job cluster. It'd be ideal if I could stripe across nodes
| and expose one big volume to all pods (JBOD style)
___________________________________________________________________
(page generated 2024-06-16 23:00 UTC)