search for: kubelet

...lly misread that - didn't realise it was on the client. 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 '10.51.70.151:/dev_static/iss3dev-static', where 'iss3dev-static' is a directory inside the gluster mount 'dev_static'. - FYI only, we are essentially mounting directories inside gluster volumes a...

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: mount failed: mount failed: exit status 1 Mounting command: mount Mounting arguments: 159.100.242.235:vol_7a...

...666 at gmail.com> > wrote: > >> >> 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: mount >> failed: mount failed: exit status 1 >> Mounting command: mount >&g...

...gt;>>> 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: mount >>>> failed: mount failed: exit status 1 >>>&gt...

...: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 > --------- -------- ----- ---- ------------- -------- ------ ------- > 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: mount > failed: mount failed: exit status 1 > Mounting command: mount > Mounting argument...

On 8 November 2017 at 02:47, Sam McLeod <mailinglists at smcleod.net> wrote: > > On 6 Nov 2017, at 3:32 pm, Laura Bailey <lbailey at redhat.com> wrote: > > Do the users have permission to see/interact with the directories, in > addition to the files? > > > Yes, full access to directories and files. > Also testing using the root user. > > > On Mon,

...>> >>> >>> 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: >>> mount failed: mount failed: exit status 1 >>> Mounting comma...

> 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 '10.51.70.151:/dev_static/iss3dev-static', where 'iss3dev-static' is a directory inside the gluster mount 'dev_static'. > - FYI only, we are essentially mounting directories inside gluster volu...

...t 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: >>>>> mount failed: mount failed: exit status 1 &gt...

...l 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: mount >>>>>> failed: mount failed: exit...

Are you seeing issue or error message which says auto_unmount option is not valid ? Can you please let me the issue you are seeing with 1.7.3 ? --Humble On Thu, Aug 10, 2017 at 3:33 PM, Christopher Schmidt <fakod666 at gmail.com> wrote: > Hi all, > > I am testing K8s 1.7.3 together with GlusterFS and have some issues > > is this correct? > - Kubernetes v1.7.3 ships

Hi all, I am testing K8s 1.7.3 together with GlusterFS and have some issues is this correct? - Kubernetes v1.7.3 ships with a GlusterFS Plugin that depends on GlusterFS 3.11 - GlusterFS 3.11 is not recommended for production. So 3.10 should be used This actually means no K8s 1.7.x version, right? Or is there anything else I could do? best Christopher -------------- next part -------------- An

...me kube-scheduler registry.centos.org/centos/kubernetes-sig-scheduler:latest # atomic install --system --system-package=no --name kube-controller-manager registry.centos.org/centos/kubernetes-sig-controller-manager:latest ### on your node(s) # atomic install --system --system-package=no --name kubelet registry.centos.org/centos/kubernetes-sig-kubelet:latest # atomic install --system --system-package=no --name kube-proxy registry.centos.org/centos/kubernetes-sig-proxy:latest Both the 1.5.x and 1.7.x sets of containers have been tested with the kubernetes ansible scripts (https://github.com/kub...

...me kube-scheduler registry.centos.org/centos/kubernetes-sig-scheduler:latest # atomic install --system --system-package=no --name kube-controller-manager registry.centos.org/centos/kubernetes-sig-controller-manager:latest ### on your node(s) # atomic install --system --system-package=no --name kubelet registry.centos.org/centos/kubernetes-sig-kubelet:latest # atomic install --system --system-package=no --name kube-proxy registry.centos.org/centos/kubernetes-sig-proxy:latest Both the 1.5.x and 1.7.x sets of containers have been tested with the kubernetes ansible scripts (https://github.com/kub...