Sidero is included as a default infrastructure provider in
clusterctl, so the
installation of both Sidero and the Cluster API (CAPI) components is as simple
as using the
Note: Because Cluster API upgrades are stateless, it is important to keep all Sidero configuration for reuse during upgrades.
Sidero has a number of configuration options which should be supplied at install
time, kept, and reused for upgrades.
These can also be specified in the
clusterctl configuration file
You can reference the
for more information on this.
For our purposes, we will use environment variables for our configuration options.
export SIDERO_CONTROLLER_MANAGER_HOST_NETWORK=true export SIDERO_CONTROLLER_MANAGER_API_ENDPOINT=192.168.1.150 clusterctl init -b talos -c talos -i sidero
First, we are telling Sidero to use
hostNetwork: true so that it binds its
ports directly to the host, rather than being available only from inside the
There are many ways of exposing the services, but this is the simplest
path for the single-node management cluster.
When you scale the management cluster, you will need to use an alternative
method, such as an external load balancer or something like
192.168.1.150 IP address is the IP address or DNS hostname as seen from the workload
In our case, this should be the main IP address of your Docker