Closed sluetze closed 5 years ago
After some more hours of debugging I found no solution but the cause. The Kubernetes version I am using is included in DockerEE. They spawn a hyperkube-container per node. Thus the packages must be available in the hyperkube-container, which they are not.
Hey Guys,
Environment: RHEL 7.6
Kubernetes 1.11 Server Version: version.Info{Major:"1", Minor:"11+", GitVersion:"v1.11.2-docker-2", GitCommit:"01c76e4d3b4fa8a0d9f51c4d2c9bfdabb0db7462", GitTreeState:"clean", BuildDate:"2018-09-05T15:54:14Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}
Images: gluster/gluster-centos:latest (also tried gluster3u12_centos7) gluster/gluster-object:latest heketi/heketi:dev
im trying to setup a gluster in kubernetes... Important: since my environment is offline (no internet connection) I manually downloaded the images and renamed them for my local registry.
I have seen the solutions around installing glusterfs-fuse... Which I already have:
kernel modules are also loaded
a manual mount from the host (yes it is the worker, which the pod is scheduled on) works!
I can reproduce this with different workers... Any Ideas?
Thanks!