Timed out waiting for pods matching '--selector=deploy-heketi=pod'

[calebpower]

So I'm having issues with deploying the deploy-heketi pod When using the gk-deploy script. To be clear, the glusterfs pod seems to deploy properly (I've looked at the issue at https://github.com/gluster/gluster-kubernetes/issues/510 but I don't think it necessarily applies here). The OS is Ubuntu 18.04, the firewall is open for the moment while we're setting stuff up, and all required kernel modules are enabled. Some troubleshooting tips would be greatly appreciated!

caleb@blocksmith-linode-02:~/gluster-kubernetes/deploy$ ./gk-deploy -gvy
Using Kubernetes CLI.

Checking status of namespace matching 'default':
default   Active   16h
Using namespace "default".
Checking for pre-existing resources...
  GlusterFS pods ...
Checking status of pods matching '--selector=glusterfs=pod':

Timed out waiting for pods matching '--selector=glusterfs=pod'.
not found.
  deploy-heketi pod ...
Checking status of pods matching '--selector=deploy-heketi=pod':

Timed out waiting for pods matching '--selector=deploy-heketi=pod'.
not found.
  heketi pod ...
Checking status of pods matching '--selector=heketi=pod':

Timed out waiting for pods matching '--selector=heketi=pod'.
not found.
  gluster-s3 pod ...
Checking status of pods matching '--selector=glusterfs=s3-pod':

Timed out waiting for pods matching '--selector=glusterfs=s3-pod'.
not found.
Creating initial resources ... /usr/bin/kubectl -n default create -f /home/caleb/gluster-kubernetes/deploy/kube-templates/heketi-service-account.yaml 2>&1
serviceaccount/heketi-service-account created
/usr/bin/kubectl -n default create clusterrolebinding heketi-sa-view --clusterrole=edit --serviceaccount=default:heketi-service-account 2>&1
clusterrolebinding.rbac.authorization.k8s.io/heketi-sa-view created
/usr/bin/kubectl -n default label --overwrite clusterrolebinding heketi-sa-view glusterfs=heketi-sa-view heketi=sa-view
clusterrolebinding.rbac.authorization.k8s.io/heketi-sa-view labeled
OK
Marking 'blocksmith-ovh-05' as a GlusterFS node.
/usr/bin/kubectl -n default label nodes blocksmith-ovh-05 storagenode=glusterfs --overwrite 2>&1
node/blocksmith-ovh-05 labeled
Marking 'blocksmith-ovh-06' as a GlusterFS node.
/usr/bin/kubectl -n default label nodes blocksmith-ovh-06 storagenode=glusterfs --overwrite 2>&1
node/blocksmith-ovh-06 labeled
Marking 'blocksmith-ovh-07' as a GlusterFS node.
/usr/bin/kubectl -n default label nodes blocksmith-ovh-07 storagenode=glusterfs --overwrite 2>&1
node/blocksmith-ovh-07 labeled
Deploying GlusterFS pods.
sed -e 's/storagenode\: glusterfs/storagenode\: 'glusterfs'/g' /home/caleb/gluster-kubernetes/deploy/kube-templates/glusterfs-daemonset.yaml | /usr/bin/kubectl -n default create -f - 2>&1
daemonset.extensions/glusterfs created
Waiting for GlusterFS pods to start ...
Checking status of pods matching '--selector=glusterfs=pod':
glusterfs-hc547   1/1   Running   0     67s
glusterfs-njxbx   1/1   Running   0     67s
glusterfs-rqxms   1/1   Running   0     67s
OK
/usr/bin/kubectl -n default create secret generic heketi-config-secret --from-file=private_key=/dev/null --from-file=./heketi.json --from-file=topology.json=topology.json
secret/heketi-config-secret created
/usr/bin/kubectl -n default label --overwrite secret heketi-config-secret glusterfs=heketi-config-secret heketi=config-secret
secret/heketi-config-secret labeled
sed -e 's/\${HEKETI_EXECUTOR}/kubernetes/' -e 's#\${HEKETI_FSTAB}#/var/lib/heketi/fstab#' -e 's/\${HEKETI_ADMIN_KEY}//' -e 's/\${HEKETI_USER_KEY}//' /home/caleb/gluster-kubernetes/deploy/kube-templates/deploy-heketi-deployment.yaml | /usr/bin/kubectl -n default create -f - 2>&1
service/deploy-heketi created
deployment.extensions/deploy-heketi created
Waiting for deploy-heketi pod to start ...
Checking status of pods matching '--selector=deploy-heketi=pod':
deploy-heketi-865f55765-bclnj   0/1   ContainerCreating   0     5m14s
Timed out waiting for pods matching '--selector=deploy-heketi=pod'.
pod not found.

Thanks in advance!

[calebpower]

das bump

[kariae]

any idea for this, having same issue on a one node kubernetes hosted on Ubuntu