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 at redhat.com> 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 at gmail.com> > wrote: > >> 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 >> 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: >> https://github.com/heketi/heketi/wiki/Kubernetes-Integration >> https://github.com/wattsteve/glusterfs-kubernetes >> >> 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 at gluster.org >> http://lists.gluster.org/mailman/listinfo/gluster-users >> > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20170726/c96437d6/attachment.html>
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 > > 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 at redhat.com> 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 at gmail.com> >> wrote: >>> >>> 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 >>> 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: >>> https://github.com/heketi/heketi/wiki/Kubernetes-Integration >>> https://github.com/wattsteve/glusterfs-kubernetes >>> >>> 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 at gluster.org >>> http://lists.gluster.org/mailman/listinfo/gluster-users >> >> >
Try adding the following lines to the deploy-heketi-deployment.yaml
and heketi-deployment.yaml files around line 53 (keeping indentation
with other similar lines):
- name: HEKETI_KUBE_NAMESPACE
value: default
Replace "default" with the namespace you're using for these pods.
Are you using gk-deploy or running the deployment manually? If the
former, and your DaemonSet is running succesfully, rerun it without
the -g flag.
--Jose
On Mon, Jul 31, 2017 at 6:20 AM, Raghavendra Talur <rtalur at redhat.com>
wrote:> 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
>>
>> 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 at
redhat.com> 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 at
gmail.com>
>>> wrote:
>>>>
>>>> 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
>>>> 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:
>>>> https://github.com/heketi/heketi/wiki/Kubernetes-Integration
>>>> https://github.com/wattsteve/glusterfs-kubernetes
>>>>
>>>> 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 at gluster.org
>>>> http://lists.gluster.org/mailman/listinfo/gluster-users
>>>
>>>
>>