News for hackers. Stuff that matters.
Re:Why Is Storage on Kubernetes So Hard? by ohiovr on Sunday January 13, 2019 @02:13PM (#18898152)
I could not figure out cluster storage with docker swarm at least. With containers springing up and going away on multiple computers I could not figure out where the volumes were supposed to “live”

The only thing that at least seemed possible without additional software was nfs mounts but I was thinking it does not help the high availability cause to see the one and only storage node go down. Nor could I see any benefits to a cluster that used the same network for file access as external network requests. Say I wanted to build a horizontally scalable video sharing site I don’t see how I could test the real world performance of it before it went live.

Re:Why Is Storage on Kubernetes So Hard? by outworlder on Sunday January 13, 2019 @03:58PM (#18898644)
You could use multiple network interfaces, one for storage, the other for the rest.

Not sure if this is in a datacenter or not. In a datacenter, you could use something like 3-PAR to have network attached storage.

But storage is hard. This is one of the advantages of using cloud providers, they have this part figured out for you. AWS's EBS volumes are network-attached storage.

Then there's another layer of abstraction when you are using containers. Ok, so you have this volume accessible from the network now, in whatever form. How do you attach it to running containers? That's what this article is about, mostly. Not with the underlying storage mechanisms.

Re:Why Is Storage on Kubernetes So Hard? by ohiovr on Sunday January 13, 2019 @04:13PM (#18898718)
I am Leary of Amazon because of the potential for sudden ruinous expenses. I looked over digital ocean and they say they are working on kubernetes but I don’t see how block storage is going to make it work. I’m just developing this on my home server for now. I’m just trying to learn the basics. Seems like cluster computing isn’t something that can be roll your own like ordinary docker can be.

Thanks for the lead though.

Re:Why Is Storage on Kubernetes So Hard? by LukeShu on Sunday January 13, 2019 @07:04PM (#18899549)
> I looked over digital ocean and they say they are working on kubernetes

FYI, Digital Ocean Kubernetes opened to everyone on December 11th.

Re:Why Is Storage on Kubernetes So Hard? by alchemism on Sunday January 13, 2019 @04:20PM (#18898760)
You can get a decent-sized cluster running free for a bit with Kubernetes Engine in Google Cloud, using the initial credits they give you. The cluster will shut off when the credits do expire.
Re:Why Is Storage on Kubernetes So Hard? by rconti on Sunday January 13, 2019 @06:55PM (#18899515)
I'm just afraid all of these volumes and resources I'm creating will be 100x easier to 'lose' and have total sprawl than it was in VM world, which already had enormous sprawl issues.
Re:Why Is Storage on Kubernetes So Hard? by rzzzt on Sunday January 13, 2019 @05:59PM (#18899263)
Clustered filesystems like Ceph or GlusterFS might help with the reliability part, but latency and bandwidth still remain a problem.

The other thing I was quite interested in at one point was flocker, a volume manager which is responsible for replicating/migrating data along with the container it is connected to. The company shut down quite a while ago but code is still available: https://github.com/ClusterHQ/flocker