gcs icon indicating copy to clipboard operation
gcs copied to clipboard

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

Results 50 gcs issues
Sort by recently updated
recently updated
newest added

In gluster/glusterd2#1324, it looks like DNS isn't ready by the time gd2 tries to resolve its own hostname. We should add an init container like etcd does to wait for...

bug

If we want to deploy multiple gcs setups on same hypervisor, we need to edit vagrant file for providing new vm-names. I think we can have some better option to...

feature

1. Need scc setup of hostpath plugin: Followed [this doc](https://docs.okd.io/latest/admin_guide/manage_scc.html#use-the-hostpath-volume-plugin) to work it around. 2. the opc cluster is on aws: the node name is like `ip-172-31-10-185.us-west-2.compute.internal` which causes problem...

bug

I am aware of many discussions where we did consider using 'loopback' devices (`losetup`) as a block device, where it just uses a file on glusterfs as backend. This has...

feature

In README under https://github.com/gluster/gcs/tree/master/deploy#deploying-an-app-with-gcs-backed-cloned-volume we should mention that one needs to change kube-node to gcs-node in https://github.com/gluster/gcs/blob/master/deploy/deploy-gcs.yml#L148.

bug

This issue is created to deploy the alert and dashboard mixins when the gcs is getting deployed.

feature

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...

steps to reproduce * delete one of the glusterd2 pod * login to the newly created pod * access glustercli commands Logs ``` time="2018-10-29 08:58:56.982656" level=warning msg="tracing: One or more...

bug

Steps performed:- 1) Created the GCS cluster:- ``` [vagrant@kube1 ~]$ kubectl get pods -n gcs NAME READY STATUS RESTARTS AGE csi-attacher-glusterfsplugin-0 2/2 Running 0 2d21h csi-nodeplugin-glusterfsplugin-45snb 2/2 Running 0 2d21h...

bug

cold reset of the cluster leads to ETCD pods going in ERROR state. 1) create a GCS cluster ``` [vagrant@kube1 ~]$ kubectl get pods -n gcs NAME READY STATUS RESTARTS...