openstack magnum on queens: please help me

Ignazio Cassano ignaziocassano at gmail.com
Sun Dec 30 10:39:08 UTC 2018


Hello Everybody,
I created a kubernetes cluster with mugnum under queens.
After that I ran the folloquing commands:

mkdir -p /root/clusters/kubecertslb/config
export KUBECONFIG=/root/clusters/kubecertslb/config
$(openstack coe cluster config kubecertslb --dir ~/clusters/kubecertslb)

Then the command "kubectl -n kube-system get po" reports:

NAME                                    READY   STATUS    RESTARTS   AGE
coredns-5864cfd79d-76889                1/1     Running   0          18h
heapster-68b976dd7-7vdlq                1/1     Running   0          18h
kubernetes-dashboard-846b8b6844-cjp2f   1/1     Running   0          18h

the command "kubectl cluster-info" reports:

Kubernetes master is running at https://10.102.186.126:6443
Heapster is running at
https://10.102.186.126:6443/api/v1/namespaces/kube-system/services/heapster/proxy
CoreDNS is running at
https://10.102.186.126:6443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy

To further debug and diagnose cluster problems, use 'kubectl cluster-info
dump'


I deployed nginx:
kubectl run nginx --image=nginx --replicas=2 --port=80


Then the command "kubectl get po" reports:
NAME                     READY   STATUS    RESTARTS   AGE
nginx-7587c6fdb6-chnw6   1/1     Running   0          18h
nginx-7587c6fdb6-m7fr2   1/1     Running   0          18h

Exposing nginx service with type NodePort works fine.
Exposing with type LoadBalancer does not work:
kubectl expose deployment nginx --target-port=80 --type=LoadBalancer

kubectl get svc:

NAME         TYPE           CLUSTER-IP     EXTERNAL-IP   PORT(S)        AGE
kubernetes   ClusterIP      10.254.0.1     <none>        443/TCP        19h
nginx        LoadBalancer   10.254.97.40   <pending>     80:31568/TCP   165m

No load balancer is created.


Im not using octavia but standard lbaas v2.
Lbaas is working fine because I tried a configuration between two ssh vm.

I read somting about the magnum.conf trust section:
someone suggested to enable "cluster_user_trust = True"

I tried it but with this parameter the kubernetes cluster does not finish:
the heat template remains in pending ang goes in timeout during the master
creation.

I read also something aboud kubernetes cloud provider must be "external" or
"openstack"
but I think it should the automatically configured by heat.

Any help, please ?

Thanks and Regards
Ignazio
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20181230/338002ea/attachment.html>


More information about the openstack-discuss mailing list