You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have an increasing number of customers deploying balenaOS virtual appliances on VMWare, Nutanix, or Azure and we currently provide them a pre-configured OVA. When delivering a few, it isn't too bad to edit the config.json file in the boot partition and export a new OVA, but for larger deployments it would be great for balenaOS to support cloud-init to at least obtain network config (IP/mask, gateway, DNS, hostname, NTP, etc) and the remainder of config.json settings via vendordata for things like balena hostnames, provisioning keys, redsocks config, CA roots, etc.
The text was updated successfully, but these errors were encountered:
We have an increasing number of customers deploying balenaOS virtual appliances on VMWare, Nutanix, or Azure and we currently provide them a pre-configured OVA. When delivering a few, it isn't too bad to edit the
config.json
file in the boot partition and export a new OVA, but for larger deployments it would be great for balenaOS to support cloud-init to at least obtain network config (IP/mask, gateway, DNS, hostname, NTP, etc) and the remainder ofconfig.json
settings viavendordata
for things like balena hostnames, provisioning keys, redsocks config, CA roots, etc.The text was updated successfully, but these errors were encountered: