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

the stack is follow ``` shell [root@master1 ~]# kubectl gluster deploy gcs.yaml /usr/local/lib/python3.6/site-packages/kubectl_gluster/main.py:68: YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as the default Loader is unsafe. Please read https://msg.pyyaml.org/load for...

One of the csi-node is keep on going to Evicted state. Below is the describe output after the pod is recreated, [vagrant@kube1 ~]$ kubectl -n gcs describe pods csi-nodeplugin-glusterfsplugin-zc9qm Name:...

bug

Signed-off-by: Poornima G

in progress

[root@benki1 ~]# kubectl get pods -ngcs NAME READY STATUS RESTARTS AGE etcd-b8smtb299s 0/1 Error 0 85s etcd-operator-77bfcd6595-h7wqf 1/1 Running 0 114s etcd-q6h6lgdj67 0/1 Running 0 102s # kubectl logs etcd-b8smtb299s...

Loop back bricks support is added in Gd2 and CSI driver. To include it in gcs following changes required. - Similar to device details, Include the bricks hosting directory in...

GCS/1.0

Not sure it's relevant, I just came across and it popped into my eyes... https://github.com/gluster/gcs/blob/177c50b9f8f53c984e20cada8d4fde7c1cc6f2a0/deploy/templates/gcs-manifests/gcs-fs-csi.yml.j2#L224 I understand https://github.com/kubernetes/kubernetes/pull/70494 as it was only meant for the registration, not for the plugin...

``` [vagrant@kube1 ~]$ kubectl describe pvc glusterblock-20 Name: glusterblock-20 Namespace: default StorageClass: glustervirtblock-csi Status: Pending Volume: Labels: Annotations: volume.beta.kubernetes.io/storage-provisioner: org.gluster.glustervirtblock Finalizers: [kubernetes.io/pvc-protection] Capacity: Access Modes: VolumeMode: Filesystem Events: Type Reason...

bug
GCS/1.0

During testing for GCS 1.0-pre, the Grafana dashboard is not displaying metrics for gluster volumes. Once GCS is deployed, I created the following workload in namespace `test`: ``` $ kubectl...

bug
GCS/1.0

When requested, GD2 pods should perform a clean shutdown. All mounted filesystems should be unmounted, and any loopback devices setup must be detached. This is required to allow safe upgrades...

GCS/1.0

https://github.com/gluster/gluster-containers/pull/126