Run work in four more kinds of cloud account (Beta)
Beta, turned on per organization. Accounts with spec.providerNebius, Denvr, Jarvis and MassedCompute
now connect with their keys, so credits you hold on those clouds run your work first.
A Nebius key names the project your credits are in and its region, and Nodus creates machines only in that
project. A Denvr key names its cluster, and a Jarvis key names a startup script you add once; the console shows
the script to copy. Nodus uses the cluster’s default VPC unless you name one, and a project’s only subnet unless
you name one.
Nodus checks those settings with the key and refuses a project, subnet, VPC or script the account does not have,
naming the field, instead of accepting a key that could never start a machine.
nodus cloud connect takes the four clouds and a repeatable --field name=value for the settings. See
Run work in your own account.