HetznerCluster
In HetznerCluster you can define everything related to the general components of the cluster as well as those properties, which are valid cluster-wide.
There are two different modes for the cluster. A pure HCloud cluster and a cluster that uses Hetzner dedicated (bare metal) servers, either as control planes or as workers.
The HCloud cluster works with Kubeadm and supports private networks.
In a cluster that includes bare metal servers there are no private networks, as this feature has not yet been integrated in cluster-api-provider-hetzner. Apart from SSH, the node image has to support cloud-init, which we use to provision the bare metal machines.
Note
In clusters with bare metal servers, you need to use this CCM, as the official one does not support bare metal.
Here you can find more information regarding the handling of SSH keys. Some of them are specified in HetznerCluster to have them cluster-wide, others are machine-scoped.
Usage without HCloud Load Balancer#
It is also possible not to use the cloud load balancer from Hetzner. This is useful for setups with only one control plane, or if you have your own cloud load balancer.
Using controlPlaneLoadBalancer.enabled=false prevents the creation of a hcloud load balancer. Then you need to configure controlPlaneEndpoint.port=6443 & controlPlaneEndpoint.host, which should be a domain that has A records configured pointing to the control plane IP for example.
If you are using your own load balancer, you need to point towards it and configure the load balancer to target the control planes of the cluster.
Overview of HetznerCluster.Spec#
Specifies details about Hetzner cloud private networks.
Cluster-wide SSH keys that serve as default for machines as well.
SSH keys for hcloud.
Reference to the secret where the SSH key for the rescue system is stored.
Details about the keys used in the data of the secret.
Set by the controller. It is the endpoint to communicate with the control plane.
Defines specs of load balancer.
Defines extra services of load balancer.
List of placement groups that should be defined in Hetzner API.
Reference to secret where Hetzner API credentials are stored.
Reference to the keys that are used in the secret, either hcloudToken or hetznerRobotUser and hetznerRobotPassword need to be specified.
Object Reference
Overview of the naming conventions of objects specific to the CAPH integration.
HCloudMachineTemplate
In HCloudMachineTemplate you can define all important properties for HCloudMachines, which are reconciled by the `HCloudMachineController`, responsible for creating and deleting servers in Hetzner Cloud.