News
BackK8s Cloud Controller Manager for cloudscale
Kubernetes setups at cloudscale can now interact even more closely with our infrastructure: Our Cloud Controller Manager (CCM) enables the enrichment of node metadata with information from our API as well as the automated use of our load balancer product.
Automatic metadata for nodes
With our CCM, your K8s cluster now knows even more about the nodes involved. Metadata about the nodes is automatically retrieved from our cloud API, e.g. the IP address(es) of the respective virtual server or its geographical region/zone. It is also possible to distinguish whether a node has been deleted or simply switched off. The compute flavor is equally available; this makes it possible, for example, to place certain workloads specifically on nodes that use a "Plus" flavor and thus have the selected number of CPU cores available for exclusive use at all times.
Our CCM is available on GitHub and supports the three latest minor releases of Kubernetes. The corresponding documentation with examples and a helper to try out the CCM in a test cluster can also be found on GitHub.
K8s services with our LBaaS feature
In addition to more detailed information about the underlying infrastructure, the CCM also enables the automated management of our LBaaS feature. To use this, select the type: LoadBalancer for a Service in Kubernetes. The load balancer can make your service accessible either from the Internet or only in one of your private networks.
The load balancer distributes incoming requests in the private network among the nodes of the K8s cluster, which do not require their own "public" interface. The permitted clients can be restricted to the desired IPs or IP ranges already at the load balancer level. In order to be able to recognize or log the IP addresses of the clients in the backend despite NAT, use the "proxy" or "proxyv2" protocol, which is supported by nginx, among others.
Our load balancer service is designed to support and simplify the operation of highly available services. However, please note that applying configuration changes via CCM may imply some downtime – approximate numbers for the different supported cases can also be found in the documentation.
Thanks to our CCM, tasks can be automated since your K8s cluster can rely on additional information about the infrastructure and on our load balancer service. This way, you not only increase the efficiency of your setup, but also the availability for your users.
Everything under control.
Your cloudscale team