similar to: Gluster Operator Design

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

Gluster Monthly Newsletter, November 2017 Come find us at KubeCon/CloudNativeCon in Austin, December 6-8! Special sessions around Storage include: Thursday, December 7 ? 11:55am - 12:30pm Kubernetes Feature Prototyping with External Controllers and Custom Resource Definitions - Tomas Smetana, Red Hat

> Clarification for below logs: > > - 'dev_static' is the gluster volume. > - 'int-kube-01' is the gluster client. > - '10.51.70.151' is the first node in a three node (2 replica, 1 arbiter) gluster cluster. > - '/var/lib/kubelet/...../iss3dev-static' is a directory on the client that should be mounting

Hi, I have the following setup in place: 1 node : RancherOS having Rancher application for Kubernetes setup 2 nodes : RancherOS having Rancher agent 1 node : CentOS 7 workstation having kubectl installed and folder cloned/downloaded from https://github.com/gluster/gluster-kubernetes using which i run Heketi setup (gk-deploy -g) I also have rancher-glusterfs-server container running with

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

> On 8 Nov 2017, at 9:03 pm, Nithya Balachandran <nbalacha at redhat.com> wrote: > > > That is not the log for the mount. Please check /var/log/glusterfs/var-lib-mountedgluster.log on the system on which you are running the mount process. > > Please provide the volume config details as well (gluster volume info) from one of the server nodes. > Oh I'm sorry, I

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

Hi Joe, On Wed, Mar 29, 2023, 12:55 PM Joe Julian <me at joejulian.name> wrote: > I was chatting with Humble about the removed gluster support for > Kubernetes 1.26 and the long deprecated CSI driver. > > I'd like to bring it back from archive and maintain it. If anybody would > like to participate, that'd be great! If I'm just maintaining it for my > own use,

Gluster 4.0! At long last, Gluster 4.0 is released! Read more at: https://www.gluster.org/announcing-gluster-4-0/ Other updates about Gluster 4.0: https://www.gluster.org/more-about-gluster-d2/ https://www.gluster.org/gluster-4-0-kubernetes/ Want to give us feedback about 4.0? We?ve got our retrospective open from now until April 11. https://www.gluster.org/4-0-retrospective/ Welcome piragua!

also I have this "split brain"? [root at glusterp1 gv0]# gluster volume heal gv0 info Brick glusterp1:/bricks/brick1/gv0 <gfid:eafb8799-4e7a-4264-9213-26997c5a4693> - Is in split-brain Status: Connected Number of entries: 1 Brick glusterp2:/bricks/brick1/gv0 <gfid:eafb8799-4e7a-4264-9213-26997c5a4693> - Is in split-brain /glusterp1/images/centos-server-001.qcow2

Gluster Monthly Newsletter, September 2017 Gluster Summit is coming! October 27-28 in Prague, Czech Republic! https://www.gluster.org/events/summit2017/ Registration is open until October 20th, 2017. Noteworthy Threads: [Gluster-devel] Proposed Protocol changes for 4.0: Need feedback. http://lists.gluster.org/pipermail/gluster-devel/2017-September/053603.html [Gluster-devel] Call for help:

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

Looking at this code, it's way more than I was looking for, too. I just need a replacement for the in-tree driver. I have a volume. I have about a half dozen pods that use that volume. I just need the same capabilities as the in-tree driver to satisfy that need. I want to use kadalu to replace the hacky thing I'm still doing using hostpath_pv, but last time I checked, it didn't build

Hi, glusterFS is working fine for large files (in most of the cases it's used for VM image store), with docker you'll generate bunch of small size files and if you want to have a good performance may be look in [1] and [2]. Also two node replica is a bit dangerous in case of high load with small files there is a good risk of split brain situation, therefore think about arbiter

On 28-Jun-2017 5:49 PM, "mabi" <mabi at protonmail.ch> wrote: Anyone? -------- Original Message -------- Subject: Persistent storage for docker containers from a Gluster volume Local Time: June 25, 2017 6:38 PM UTC Time: June 25, 2017 4:38 PM From: mabi at protonmail.ch To: Gluster Users <gluster-users at gluster.org> Hello, I have a two node replica 3.8 GlusterFS

I was chatting with Humble about the removed gluster support for Kubernetes 1.26 and the long deprecated CSI driver. I'd like to bring it back from archive and maintain it. If anybody would like to participate, that'd be great! If I'm just maintaining it for my own use, then so be it. ? It has been archived for 4 years, so it's going to need a bit of work. I also don't

Joe, Agree with you on turning this around into something more positive. One aspect that would really help us decide on our next steps here is the actual number of deployments that will be affected by the removal of the gluster driver in Cinder. If you are running or aware of a deployment of OpenStack Cinder & Gluster, can you please respond on this thread or to me & Niels in private

Gluster Monthly Newsletter, August 2017 -- Great news! We?ve released 3.12! https://www.gluster.org/3-12/announcing-glusterfs-release-3-12-0-long-term-maintenance/ This is a major release that will be Long Term Stable. Notable feature highlights are: - Ability to mount sub-directories using the Gluster native protocol (FUSE) - Brick multiplexing enhancements that help scale