vxav

1. Docker via GS VPN

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}

vxav

# 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 account

vxav

Interesting docs links

• CAPM3 docs
• Metal3 book (very good)

---

Testing / Observations

(List of states)

vxav

Bare 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.

• Install the Redfish-Interop-Validator tool

pip install redfish_interop_validator

vxav

Step 1

1. In <wc>/mapi/clusters/kustomization.yaml:

resources:
  - ../../../../../../../../bases/cluster
  - ../../../../../../../../bases/apps/default_step1

2. In staging.yaml > Update default_apps_release to 0.11.0.

vxav

Bill of materials

• ESP8266 - 2.32€: Controller
• ADS1115 - 1,92€: ADC board to have more analog input and better resolution.
• pH Sensor and circuit board:
• [DFRobot ph sensor kit](https://www.df

vxav

Ignition logs

journalctl --identifier=ignition --all

Query metadata

/usr/share/oem/bin/vmtoolsd --cmd "info-get guestinfo.ignition.config.data" | base64 -d

vxav

Running Kubernetes 1.24 with CAPVCD.

❗ This is tested with Vanilla Kubernetes nodes, it may not work with Tanzu.

Image-builder

• Clone the image-builder repo.
• Edit images/capi/ansible/node.yml
• Add the following tasks at the end (e.g. before the sysprep section)