use gluster-kubernetes to gcs deployment - Githubissues

gluster / gcs

Check github.com/heketi, github.com/gluster/gluster-containers, or github.com/kadalu/kadalu as active alternatives

https://gluster.org

Apache License 2.0

36 stars 24 forks source link

use gluster-kubernetes to gcs deployment #81

Open Madhu-1 opened 5 years ago

Madhu-1 commented 5 years ago

currently, we are using kubespray for deployment of kubernetes cons of using this are:

kubespray is maintained by different teams (if we face any issue we need to wait for the new release)
kubespray currently does not support latest released kubernetes version( Kube 1.13.0) we have to wait for them to release a support for Kube latest version

if we make use of current deployment scripts used for heketi-gd1 (https://github.com/gluster/gluster-kubernetes) pros:

we are not dependent on the third-party module (kubespray) to deploy GCS
we already have some test cases in the gluster-kubernetes repo (we can make use of it)

@atinmu @kshlm @JohnStrunk @obnoxxx want to know your thoughts on this.

JohnStrunk commented 5 years ago

g-k uses kubeadm directly whereas kubespray uses kubeadm internally. I also have a repo that brings up a cluster w/ kubeadm and I find keeping up w/ the changes to be a pain.

I guess we need to decide what our goal is... If we want a stable kube cluster that's easy to maintain, kubespray is probably the future. If we want to chase the edge, kubeadm + custom tooling would let us do that.

Using g-k won't be free (the Vagrant environment is currently broken, at least for me).