c39df2f7da
* openstack * rename to base_name * fix openstack boot vtpm * add docs for accessing bootstrapper logs * rename to initial count
1.5 KiB
Debug cluster
A debug cluster allows quicker iteration cycles during development by being able to upload new bootstrapper binaries through the cdbg tool.
Furthermore, a debug cluster allows you to access the bootstrapper logs through the cloud providers serial console.
Creating a debug cluster
After building (see here), you can find all CLIs and binaries in the build directory.
The cluster creation mostly follows the official docs instructions, but varies slightly in the following steps:
./constellation config generate <CSP>
by default uses the referenced nightly image.
To replace them with the latest debug image, run
bazel run //internal/api/versionsapi/cli -- latest --ref main --stream debug
to fetch the latest version and insert in the image field of the config file.
Before cluster creation you need to configure the cluster as debug.
Set debugCluster: true in the config:
yq eval -i '.debugCluster=true' constellation-conf.yaml
Fetch measurements for the debug image:
./constellation config fetch-measurements --insecure
Create the cluster and deploy the debug images:
./constellation create ...
./cdbg deploy
Finally run:
./constellation init
Access bootstrapper logs
Once logged in to the control-plane machine, execute:
journalctl -fu constellation-bootstrapper