Gluster’s management in k8s

Amar Tumballi
Jul 5 · 2 min read

A talk @ DevConf.IN’19

Abstract: This blog gives a small snippet into the talk we are giving in DevConf.IN’19. Goes little deep into Gluster project details.


The back story

It was some time in 2018, GD2 development was actively happening. Aravinda had just gotten into this team. On one of our weekly twice carpool time, he asked a question which made both of us think a lot (carpooling in Bangalore gives a lot of time think 😃), and feel the ‘Aha!’ moment. He asked, “If GD2 is developed solely to solve the k8s usecase, why don’t we handle it without gluster’s management layer?”


DevConf.IN’19

As we approached 2019, our GD2 development was almost stagnant. And there were projects like rook.io which got more attention, and rightly so. They solved the storage problems better than ‘previously’ available solutions. While Gluster had its share of users consuming the project in k8s, it used heketi project for this solution.

Aravinda: “If GD2 is developed solely to solve the k8s usecase, why don’t we handle it without gluster’s management layer?”

Me: ‘Why Not?’

As part of the talk, we would like to showcase how this idea can be achieved, how Gluster can make storage ‘Easy’ for you in k8s ecosystem. We have been busy over weekends prototyping, and hoping to have a working model. It would be fantastic to get feedback from you. Any feedback on the idea, implementation, or usability is greatly appreciated.

Thanks to Sac Urs.

Amar Tumballi

Written by

#gluster #kannada #life