search for: daemonset

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

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 try deploying heketi using heketi-deployment.json spec file, > I end up with a CrashLoopBackOff pod. > > > # kubectl get pods > > NA...

...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 following error: # kubectl logs deploy-heketi-930916695-np4hb Heketi v4.0.0-8-g9372c22-release-4 [kubeexec] ERROR 2017/07/21 06:08:52 /src/ github.com/heketi/heketi/executors/kubeexec/kubeexec.go:125: Namespace must be provid...

...d 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 > following error: > > # kubectl logs deploy-heketi-930916695-np4hb > > Heketi v4.0.0-8-g9372c22-release-4 > > [kubeexec] ERROR 2017/07/21 06:08:52 /src/github.com/heketi/heketi/ > executors/kube...

...k-deploy -g', in the Rancher console, i see the following error: Readiness probe failed: Failed to get D-Bus connection: Operation not permitted >From the attached gk-deploy_log i see that it failed at: Waiting for GlusterFS pods to start ... pods not found. In the kube-templates/glusterfs-daemonset.yaml file, i see this for Readiness probe section: ------------------------------------------------------------------ readinessProbe: timeoutSeconds: 3 initialDelaySeconds: 40 exec: command: - "/bin/bash" - "-c...