Policy pods reports CrashLoopBackOff on worker nodes

[libujacob]

When I start genie-complete.yaml, the genie-policy-controller pods on worker nodes are reporting CrashLoopBackOff error. This pod is working fine on master nodes.

root@net-iso-1:~# kubectl apply -f https://raw.githubusercontent.com/cni-genie/CNI-Genie/master/conf/1.8/genie-complete.yaml
clusterrole.rbac.authorization.k8s.io/genie-plugin created
clusterrole.rbac.authorization.k8s.io/genie-policy created
clusterrolebinding.rbac.authorization.k8s.io/genie-plugin created
clusterrolebinding.rbac.authorization.k8s.io/genie-policy created
serviceaccount/genie-plugin created
serviceaccount/genie-policy created
configmap/genie-config created
daemonset.apps/genie-plugin created
daemonset.apps/genie-network-admission-controller created
service/genie-network-admission-controller created
daemonset.apps/genie-policy-controller created
root@net-iso-1:~# 
root@net-iso-1:~# kubectl get po --all-namespaces
NAMESPACE     NAME                                       READY   STATUS             RESTARTS   AGE
kube-system   coredns-66bff467f8-b4tf8                   1/1     Running            0          4d
kube-system   coredns-66bff467f8-x9scn                   1/1     Running            0          4d
kube-system   etcd-net-iso-1                             1/1     Running            0          4d
kube-system   genie-network-admission-controller-px8k7   1/1     Running            0          89s
kube-system   genie-plugin-7mh8b                         1/1     Running            0          89s
kube-system   genie-plugin-j7l7d                         1/1     Running            0          89s
kube-system   genie-policy-controller-9qdrv              0/1     CrashLoopBackOff   3          89s
kube-system   genie-policy-controller-cv2z4              1/1     Running            0          89s
kube-system   kube-apiserver-net-iso-1                   1/1     Running            0          4d
kube-system   kube-controller-manager-net-iso-1          1/1     Running            0          4d
kube-system   kube-flannel-ds-amd64-sspfc                1/1     Running            0          3d19h
kube-system   kube-flannel-ds-amd64-vmfwd                1/1     Running            0          3d19h
kube-system   kube-proxy-czcg9                           1/1     Running            0          4d
kube-system   kube-proxy-wlvvz                           1/1     Running            0          4d
kube-system   kube-scheduler-net-iso-1                   1/1     Running            0          4d
kube-system   weave-net-69znn                            2/2     Running            0          4d
kube-system   weave-net-7p2j5                            2/2     Running            1          4d
root@net-iso-1:~# 

Looks like the pod is looking for the config file to reach the api-server and it is missing in the worker nodes and thus failing.