Added more docs about node labels and how to start kubelet
1 file changed
tree: 83b0510d73afa36e19c3cf0a4d4774e80667d844
  1. .gitignore
  2. Dockerfile
  3. LICENSE-2.0
  4. Makefile
  6. cloudstack.go
  7. cloudstack_instances.go
  8. cloudstack_loadbalancer.go
  9. cloudstack_test.go
  10. cmd/
  11. deployment.yaml
  12. go.mod
  13. go.sum
  14. metadata.go
  15. metadata_linux.go
  16. metadata_other.go
  17. service.yaml
  18. vendor/

Cloudstack Cloud Controller Manager

A Cloud Controller Manager to facilitate Kubernetes deployments on Cloudstack.

Based on the old Cloudstack provider in Kubernetes that will be removed soon.


There are several notable differences from the old cloud provider that need to be taken into account when migrating to the standalone provider.

Load Balancer

Load balancer rule names now include the protocol as well as the LB name and service port. This was added to distinguish tcp, udp and tcp-proxy service operating on the same port. Without this change, it would not be possible to map, for example, a service that runs on both TCP and UDP port 8000.

:warning: If you have existing rules, remove them before upgrading and add them back afterwards.

If you don't do this, you need to manually remove the rules in CloudStack when they are replaced.


When kubelet still contained cloud provider code, node metadata was fetched from the DHCP server on the instance's Virtual Router.

This is no longer possible with the standalone cloud controller, so all metadata now comes from the Cloudstack API. Some metadata may be missing or wrong, please file bugs when this happens to you.

Node Labels

It is recommended to launch kubelet with the following parameter:

This will treat the node as ‘uninitialized’ and cause the CCM to apply metadata labels from CloudStack automatically.

Supported labels are:

  • (= the instance name)
  • (= the compute offering)
  • (= the zone)
  • (also = the zone)

It is also possible to trigger this process manually by issuing the following command:

kubectl taint nodes <my-node-without-labels>


All dependencies are vendored. You need GNU make, git and Go 1.11 to build cloudstack-ccm.

It's still possible to build with Go 1.10, but you need to remove the option -mod vendor from the cloudstack-ccm compilation target in the Makefile.

go get
cd ${GOPATH}/src/

To build the cloudstack-cloud-controller-manager container, please use the provided Docker file:

docker build . -t swisstxt/cloudstack-cloud-controller-manager:latest


Prebuilt containers are posted on Docker Hub.


To deploy the ccm in the cluster see deployment.yaml and configure your cloudstack and api server connection. See the comments.


This CCM supports TCP, UDP and TCP-Proxy LoadBalancer deployments.

For UDP and Proxy Protocol support, CloudStack 4.6 or later is required.

Since kube-proxy does not support the Proxy Protocol or UDP, you should connect this directly to containers, for example by deploying a DaemonSet and setting hostNetwork: true.

See service.yaml for an example Service deployment and part of a suitable configuration for an ingress controller.


Make sure your apiserver is running locally and keep your cloudstack config ready:

./cloudstack-ccm --cloud-provider external-cloudstack --cloud-config cloud.config --master localhost


© 2018 SWISS TXT AG and the Kubernetes authors.

See LICENSE-2.0 for permitted usage.