Magnum Kubernetes openstack-cloud-controller-manager unable not resolve master node by DNS

Pawel Konczalski pawel.konczalski at everyware.ch
Wed May 8 19:27:32 UTC 2019


Hi Bharat,

i was able to deploy the Kubernetes cluster with Magnum after update / 
specify Kubernetes version with the "--labels kube_tag=v1.13.4" 
parameter. See:

# kube_tag
https://docs.openstack.org/magnum/latest/user/#kube-tag
https://hub.docker.com/r/openstackmagnum/kubernetes-apiserver/tags/

# cloud_provider_tag
https://docs.openstack.org/magnum/latest/user/#cloud-provider-tag
https://hub.docker.com/r/k8scloudprovider/openstack-cloud-controller-manager/tags/

This may by related with this issue:
https://github.com/kubernetes/cloud-provider-openstack/issues/280


# openstack coe cluster template create kubernetes-cluster-template \
   --image "Fedora AtomicHost 29" \
   --external-network public \
   --dns-nameserver 8.8.8.8 \
   --master-flavor m1.kubernetes \
   --flavor m1.kubernetes \
   --coe kubernetes \
   --volume-driver cinder \
   --network-driver flannel \
   --docker-volume-size 25 \
   --public \
   --labels kube_tag=v1.13.4,cloud_provider_tag=1.13.1


# openstack coe cluster create kubernetes-cluster \
   --cluster-template kubernetes-cluster-template \
   --master-count 1 \
   --node-count 2 \
   --keypair mykey


# kubectl get pods --all-namespaces -o wide
NAMESPACE     NAME                                       READY STATUS    
RESTARTS   AGE     IP NODE                                        
NOMINATED NODE READINESS GATES
kube-system   coredns-dcc6d487d-hxpgq                    1/1 Running   
0          7h55m   10.100.9.2 
kubernetes-cluster7-sysemevhbq4i-minion-1   <none> <none>
kube-system   coredns-dcc6d487d-nkb9p                    1/1 Running   
0          7h57m   10.100.78.4 
kubernetes-cluster7-sysemevhbq4i-minion-0   <none> <none>
kube-system   heapster-796547984d-6wgwp                  1/1 Running   
0          7h57m   10.100.78.2 
kubernetes-cluster7-sysemevhbq4i-minion-0   <none> <none>
kube-system   kube-dns-autoscaler-7865df57cd-ln4cc       1/1 Running   
0          7h57m   10.100.78.3 
kubernetes-cluster7-sysemevhbq4i-minion-0   <none> <none>
kube-system   kubernetes-dashboard-f5496d66d-tdbvv       1/1 Running   
0          7h57m   10.100.78.5 
kubernetes-cluster7-sysemevhbq4i-minion-0   <none> <none>
kube-system   openstack-cloud-controller-manager-9s5wh   1/1 Running   
3          7h57m   10.0.0.10 kubernetes-cluster7-sysemevhbq4i-master-0   
<none> <none>

Thank you

Pawel


Am 08.05.19 um 8:40 vorm. schrieb Bharat Kunwar:
> Try using the latest version, think there is an OCCM_TAG.
>
> Sent from my iPhone
>
>> On 7 May 2019, at 20:10, Pawel Konczalski <pawel.konczalski at everyware.ch> wrote:
>>
>> Hi,
>>
>> i try to deploy a Kubernetes cluster with OpenStack Magnum but the openstack-cloud-controller-manager pod fails to resolve the master node hostname.
>>
>> Does magnum require further parameter to configure the DNS names of the master and minions? DNS resolution in the VMs works fine. Currently there is no Designate installed in the OpenStack setup.
>>
>>
>> openstack coe cluster template create kubernetes-cluster-template1 \
>>    --image Fedora-AtomicHost-29-20190429.0.x86_64 \
>>    --external-network public \
>>    --dns-nameserver 8.8.8.8 \
>>    --master-flavor m1.kubernetes \
>>    --flavor m1.kubernetes \
>>    --coe kubernetes \
>>    --volume-driver cinder \
>>    --network-driver flannel \
>>    --docker-volume-size 25
>>
>> openstack coe cluster create kubernetes-cluster1 \
>>    --cluster-template kubernetes-cluster-template1 \
>>    --master-count 1 \
>>    --node-count 2 \
>>    --keypair mykey
>>
>>
>> # kubectl get pods --all-namespaces -o wide
>> NAMESPACE     NAME                                       READY STATUS             RESTARTS   AGE       IP NODE                                         NOMINATED NODE
>> kube-system   coredns-78df4bf8ff-mjp2c                   0/1 Pending            0          36m       <none> <none>                                       <none>
>> kube-system   heapster-74f98f6489-tgtzl                  0/1 Pending            0          36m       <none> <none>                                       <none>
>> kube-system   kube-dns-autoscaler-986c49747-wrvz4        0/1 Pending            0          36m       <none> <none>                                       <none>
>> kube-system   kubernetes-dashboard-54cb7b5997-sk5pj      0/1 Pending            0          36m       <none> <none>                                       <none>
>> kube-system   openstack-cloud-controller-manager-dgk64   0/1 CrashLoopBackOff   11         36m       <none> kubernetes-cluster1-vulg5fz6hg2n-master-0   <none>
>>
>>
>> # kubectl -n kube-system logs openstack-cloud-controller-manager-dgk64
>> Error from server: Get https://kubernetes-cluster1-vulg5fz6hg2n-master-0:10250/containerLogs/kube-system/openstack-cloud-controller-manager-dgk64/openstack-cloud-controller-manager: dial tcp: lookup kubernetes-cluster1-vulg5fz6hg2n-master-0 on 8.8.8.8:53: no such host
>>
>>
>> BR
>>
>> Pawel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5227 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20190508/af3d2e20/attachment-0001.bin>


More information about the openstack-discuss mailing list