# Unable to create k3s downstream cluster with node provider Openstack and external cloud-controller-manager

**URL:** <https://forums.suse.com/t/unable-to-create-k3s-downstream-cluster-with-node-provider-openstack-and-external-cloud-controller-manager/37922>\
**Category:** SUSE Rancher Prime\
**Created:** [May 17, 2022, 2:25pm UTC](https://forums.suse.com/t/unable-to-create-k3s-downstream-cluster-with-node-provider-openstack-and-external-cloud-controller-manager/37922 "2022-05-17T14:25:15Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![maybebuggy](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/maybebuggy/32/7983_2.png) [@maybebuggy](https://forums.suse.com/u/maybebuggy)\
**Post date:** [May 17, 2022, 2:25pm UTC](https://forums.suse.com/t/unable-to-create-k3s-downstream-cluster-with-node-provider-openstack-and-external-cloud-controller-manager/37922/1 "2022-05-17T14:25:15Z")

</div>

Hi,

I’m struggling with creating a downstream k3s cluster (rke2 as well) on Openstack (via Openstack node driver) and an external cloud-controller-manager ([cloud-provider-openstack/using-openstack-cloud-controller-manager.md at master · kubernetes/cloud-provider-openstack · GitHub](https://github.com/kubernetes/cloud-provider-openstack/blob/master/docs/openstack-cloud-controller-manager/using-openstack-cloud-controller-manager.md))

I was able to do that for an RKE (v1) cluster, as there is a UI form for the cloud-controller-manager and there I put just “external” and the nodes booted and were tainted as expected. For K3S I tried several variants of adding advanced additional arguments for kubelet, apiserver and controller manager (cloud-provider=external for each of them) but the nodes still came up untainted and deploying the ccm anyway resulted in failures (address already in use issues for the OCCM on some high port)

Any idea how that could be achieved?

Thanks in advance  
Greetings  
.sascha