similar to: Unable to use Heketi setup to install Gluster for Kubernetes

Adding more people to the thread. I am currently not able to analyze the logs. On Thu, Jul 27, 2017 at 5:58 AM, Bishoy Mikhael <b.s.mikhael at gmail.com> wrote: > Hi Talur, > > I've successfully got Gluster deployed as a DaemonSet using k8s spec file > glusterfs-daemonset.json from > https://github.com/heketi/heketi/tree/master/extras/kubernetes > > but then when I

Hi Talur, I've successfully got Gluster deployed as a DaemonSet using k8s spec file glusterfs-daemonset.json from https://github.com/heketi/heketi/tree/master/extras/kubernetes but then when I try deploying heketi using heketi-deployment.json spec file, I end up with a CrashLoopBackOff pod. # kubectl get pods NAME READY STATUS RESTARTS AGE

Hi Bishoy, Adding Talur who can help address your queries on Heketi. @wattsteve's github repo on glusterfs-kubernetes is a bit dated. You can either refer to gluster/gluster-kubernetes or heketi/heketi for current documentation and operational procedures. Regards, Vijay On Fri, Jul 21, 2017 at 2:19 AM, Bishoy Mikhael <b.s.mikhael at gmail.com> wrote: > Hi, > > I'm

Hi, I'm trying to deploy Gluster and Heketi on a Kubernetes cluster I'm following the guide at https://github.com/gluster/gluster-kubernetes/ but the video referenced in the page is showing json files used while the git repo has only yaml files, they are quiet similar though, but Gluster is a deployment not a DaemonSet. I deploy Gluster DaemonSet successfully, but heketi is giving me the

On Thu, Aug 10, 2017 at 10:25 PM, Christopher Schmidt <fakod666 at gmail.com> wrote: > Just created the container from here: https://github.com/gluster/ > gluster-containers/tree/master/CentOS > > And used stock Kubernetes 1.7.3, hence the included volume plugin and > Heketi version 4. > > ? Regardless of the glusterfs client version this is supposed to work. One patch

As an another solution, if you are updating the system where you run application container to latest glusterfs ( 3.11) , this will be fixed as well as it support this mount option. --Humble On Thu, Aug 10, 2017 at 10:39 PM, Christopher Schmidt <fakod666 at gmail.com> wrote: > Ok, thanks. > > Humble Devassy Chirammal <humble.devassy at gmail.com> schrieb am Do., 10. >

Yes, I tried to, but I didn't find a 3.11 centos-release-gluster package for CentOS. Humble Devassy Chirammal <humble.devassy at gmail.com> schrieb am Do., 10. Aug. 2017, 19:17: > As an another solution, if you are updating the system where you run > application container to latest glusterfs ( 3.11) , this will be fixed as > well as it support this mount option. > >

Just created the container from here: https://github.com/gluster/gluster-containers/tree/master/CentOS And used stock Kubernetes 1.7.3, hence the included volume plugin and Heketi version 4. Humble Devassy Chirammal <humble.devassy at gmail.com> schrieb am Do., 10. Aug. 2017, 18:49: > ?Thanks .. Its the same option. Can you let me know your glusterfs client > package version ?? >

Ok, thanks. Humble Devassy Chirammal <humble.devassy at gmail.com> schrieb am Do., 10. Aug. 2017, 19:04: > On Thu, Aug 10, 2017 at 10:25 PM, Christopher Schmidt <fakod666 at gmail.com> > wrote: > >> Just created the container from here: >> https://github.com/gluster/gluster-containers/tree/master/CentOS >> >> And used stock Kubernetes 1.7.3, hence the

?Thanks .. Its the same option. Can you let me know your glusterfs client package version ?? On Thu, Aug 10, 2017 at 8:34 PM, Christopher Schmidt <fakod666 at gmail.com> wrote: > > short copy from a kubectl describe pod... > > Events: > FirstSeen LastSeen Count From SubObjectPath Type Reason Message > --------- -------- ----- ---- ------------- -------- ------

short copy from a kubectl describe pod... Events: FirstSeen LastSeen Count From SubObjectPath Type Reason Message --------- -------- ----- ---- ------------- -------- ------ ------- 5h 54s 173 kubelet, k8s-bootcamp-rbac-np-worker-6263f70 Warning FailedMount (combined from similar events): MountVolume.SetUp failed for volume "pvc-fa4b2621-7dad-11e7-8a44-062df200059f" : glusterfs:

Getting this answer back on the list in case anyone else is trying to share storage. Thanks for the docs pointer, Tanner. -John On Thu, Sep 7, 2017 at 6:50 PM, Tanner Bruce <tanner.bruce at farmersedge.ca> wrote: > You can set a security context on your pod to set the guid as needed: > https://kubernetes.io/docs/tasks/configure-pod-container/security-context/ > > > This

Hello, I am trying to setup GitLab, Redis and PostgreSQL containers in Kubernetes using Gluster for persistence. GlusterFS nodes are setup on machines (CentOS) external to Kubernetes cluster (running on RancherOS host). Issue is that when GitLab tries starting up, the login page doesn't load. It's a fresh setup and not something that stopped working now. root at

Heketi v5.0.1 is now available. This release[1] fixes a flaw that was found in heketi API that permits issuing of OS commands through specially crafted requests, possibly leading to escalation of privileges. More details can be obtained at CVE-2017-15103. [2] If authentication is turned "on" in heketi configuration, the flaw can be exploited only by those who possess authentication

Hi all, Wondered if there are others in the community using GlusterFS on Google Compute Engine and Kubernetes via Google Container Engine together. We're running glusterfs 3.7.6 on Ubuntu Xenial across 3 GCE nodes. We have a single replicated volume of ~800GB that our pods running in Kubernetes are mounting. We've observed a pattern of soft lockups on our Kubernetes nodes that mount our

Hi all, Heketi v6.0.0 is now available [1]. This is the new stable version of Heketi. Older versions are discontinued. The main additions in this release are the block-volume API, a great deal of stabilization to prevent inconsistent database and out-of-sync situations, and tooling to do disaster recovery when the database is bad. Changelog * Add support for gluster-block volumes * Add device

Hello, I have a gluster cluster with 4 nodes, that is managed using heketi. I want to test the removeal of one node. We have several volumes on it, some with rep=2, others with rep=3. I get the following error: [root at CTYI1458 .ssh]# heketi-cli --user admin --secret "******" node remove 749850f8e5fd23cf6a224b7490499659 Error: Failed to remove device, error: Cannot replace brick

Hi, just out of curiosity why? Is it a personal challenge? On 9/22/20 1:37 PM, Andrea Cucciarre' via samba wrote: > Hello, > > I have successfully (hopefully) configured samba to run in Kubernetes > pods, basically I have a pod (i.e. container) that run winbindd and join > the Windows AD, and a pod (i.e. container) that run smbd. > I have used socat to allow the unix

Hello, I have successfully (hopefully) configured samba to run in Kubernetes pods, basically I have a pod (i.e. container) that run winbindd and join the Windows AD, and a pod (i.e. container) that run smbd. I have used socat to allow the unix socket communication between winbindd and smbd pods: *** winbindd pod *** UID??????? PID? PPID? C STIME TTY????????? TIME CMD root???????? 1???? 0? 0

Hello, Is it possible to set up a Heketi Managed gluster cluster in one datacenter, and then have geo replication for all volumes to a second cluster in another datacenter? I've been looking at that, but haven't really found a recipe/solution for this. Ideally what I want is that when a volume is created in cluster1, that a slave volume is automatically created in cluster2, and