If true, then the hardware module requires an atemsys device to run.

The hostname of the node that this hardware module should run on.

If true, then the hardware module runs with realtime priority.

The hardware module config in raw bytes to tbe used by the installer service.

If true, then the hardware module runs with normal cluster networking. if false, then the hardware module runs with host network interfaces.

If true, then the hardware module is running the EtherCAT OSS stack. and requires access to the /dev/EtherCAT0 device file.

fully qualified url to container registry, e.g. 'gcr.io/'

image name, will also be used in the template for the resources that run the image (e.g. pod or deployment)

image ref, e.g. '@sha256:' or ':'

private registry auth, e.g. for gcr.io use: user=oauth2accesstoken password="$(gcloud auth application-default print-access-token)"

The addon name - must be a valid dns name - should not start with 'skill-' - the combination of (type,name) must be unique the generated namespace will by '$type-$name' Prefer to specify id instead of name

The type of the addon, will determine the supported options

The addon id - must be a valid id in. This must: - start with a letter in the alphabet - only contain [a-Z0-9._] - we recommend using reverse dns notation - should not start with 'skill-' - the combination of (type,name) must be unique the generated namespace will by '$type-$name'

The semver version of the addon. Uses 0.0.1 if unspecified.

The addon name. Prefer to specify id instead of name

The type of the addon

The id of the addon