Re: gluster-heketi-kubernetes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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

deploy-heketi-930916695-tq4ks   0/1       CrashLoopBackOff   11         35m



kubectl describe gives me the following error:


Warning FailedSync Error syncing pod, skipping: failed to "StartContainer" for "deploy-heketi" with CrashLoopBackOff: "Back-off 20s restarting failed container=deploy-heketi pod=deploy-heketi-930916695-qpngx_default(f97e7bdc-6dd5-11e7-b8b5-3cfdfea552a8)"



and the pod logs are as follows:


# kubectl logs deploy-heketi-930916695-qpngx

Heketi v4.0.0-8-g9372c22-release-4

[kubeexec] ERROR 2017/07/21 05:37:11 /src/github.com/heketi/heketi/executors/kubeexec/kubeexec.go:125: Namespace must be provided in configuration: File /var/run/secrets/kubernetes.io/serviceaccount/namespace not found

[heketi] ERROR 2017/07/21 05:37:11 /src/github.com/heketi/heketi/apps/glusterfs/app.go:85: Namespace must be provided in configuration: File /var/run/secrets/kubernetes.io/serviceaccount/namespace not found

ERROR: Unable to start application



so what am I missing here?


On Mon, Jul 24, 2017 at 6:14 AM, Vijay Bellur <vbellur@xxxxxxxxxx> wrote:
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@xxxxxxxxx> wrote:
Hi,

I'm trying to deploy Gluster and Heketi on a Kubernetes cluster
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 provided in configuration: File /var/run/secrets/kubernetes.io/serviceaccount/namespace not found

[heketi] ERROR 2017/07/21 06:08:52 /src/github.com/heketi/heketi/apps/glusterfs/app.go:85: Namespace must be provided in configuration: File /var/run/secrets/kubernetes.io/serviceaccount/namespace not found

ERROR: Unable to start application


What am I doing wrong here?!

I found more than one source for documentation about how to use Gluster as a persistent storage for kubernetes, some of them are:

Which one to follow?!

Also I've created a topology file as noted by one of the documentation, but I don't know how to provide it to heketi.

Regards,
Bishoy Mikhael

_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-users


_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-users

[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux