[atomic] issue with keystone pod in k8s deployment

Hello,

I’am running openstack ussuri on ubuntu 18.04, openstack is working fine.

i have setup magnum following the official documentation for ussuri and i am trying to start a k8s cluster following the instructions here : https://docs.openstack.org/magnum/latest/install/launch-instance.html

however it seems the keytone pod is failing to start due to a missing configuration option

[fedora k8s-cluster-tejbzdx56ltd-master-0 heat-config]$ kubectl logs k8s-keystone-auth-pgs57  -n kube-system

W1026 14:23:56.037829       1 config.go:73] Argument --sync-config-file or --sync-configmap-name missing. Data synchronization between Keystone and Kubernetes is disabled.

I1026 14:23:56.062738       1 keystone.go:537] Creating kubernetes API client.

W1026 14:23:56.062822       1 client_config.go:541] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.

I1026 14:23:56.092241       1 keystone.go:554] Kubernetes API client created, server version v1.15

E1026 14:23:56.105032       1 main.go:60] failed to parse policies defined in the configmap k8s-keystone-auth-policy: json: cannot unmarshal object into Go value of type keystone.policyList

the cluster nodes, appear to start but due to that keystone error some service are not working, such as the dashboard wich is also crashed :

Internal Server Error: "/": Post https://127.0.0.1:8443/webhook?timeout=30s: dial tcp 127.0.0.1:8443: connect: connection refused

it appear to be a known issue due to a different version in kubectl tools, but my knowledge of k8s isnt deep enough to find a workaround there.

thanks for any help

see https://serverfault.com/questions/1040113/keystone-auth-pod-fail-to-start-on-k8s-cluster-on-magnum-openstack-ussuri

Michael