Kamaji allows to run control plane components in pods in the MC rather than dedicating nodes in the WC (doc).
Those pods are controlled through tenantcontrolplanes.kamaji.clastix.io CRs which are reconciled by the kamaji controller.
Kamaji allows to run control plane components in pods in the MC rather than dedicating nodes in the WC (doc).
Those pods are controlled through tenantcontrolplanes.kamaji.clastix.io CRs which are reconciled by the kamaji controller.
If running Kind in a VM accessible via GS VPN (e.g. Neoedge), you must change the docker bridge network or it will set it to 172.18.0.0 which conflicts with our Gridscale VPN endpoint.
Set this in /etc/docker/daemon.json
{
"default-address-pools":[
{"base":"10.253.0.0/16","size":24}# openssl genrsa -out sa.key 2048
# openssl rsa -in sa.key -pubout -out sa.pub
export RESOURCE_GROUP="glean"
export LOCATION="westeurope"
export AZURE_STORAGE_ACCOUNT="oidcissuer$(openssl rand -hex 4)"
export AZURE_STORAGE_CONTAINER="oidc-test"
# Create Azure blob storage and accountBare metal servers have different BMCs with different redfish feature sets.
Metal3 relies on Ironic to integrate with the BMC via Redfish.
We can check that a server is compliant with the Ironic feature set using Redfish-Interop-Validator.
pip install redfish_interop_validator
Ignition logs
journalctl --identifier=ignition --all
Query metadata
/usr/share/oem/bin/vmtoolsd --cmd "info-get guestinfo.ignition.config.data" | base64 -d
❗ This is tested with Vanilla Kubernetes nodes, it may not work with Tanzu.
images/capi/ansible/node.yml