This message was deleted.
# harvester
a
This message was deleted.
s
I'm unclear about this also. I've run though the manual ISO installation and it presents an option to provide a link to the configuration over https after you fill out all the required fields - defeating the purpose of the static configuration IMO. A much cleaner semi-manual install experience would be a prompt to specify the configuration at the start, and then the ability to fill out any fields which weren't provided in the static config via guided prompt.
๐Ÿ™Œ 2
g
for automated installs using config url the best option is to ipxe boot the vm's
we need to define networking before the api call to fetch config url can be downloaded
๐Ÿ‘ 1
ipxe works because the kernel arguments already instruct how to configure network
t
If you can drop into grub and edit the kernel command line options, you might be able to pass in the URL the same as if you booted off PXE. I haven't done it yet, but I'd try something adding something like this: harvester.install.automatic=true harvester.install.config_url=https://1.2.3.4/config.yaml ip=dhcp I am using something similar to boot an automated install off a hard disk image using grub.
๐Ÿ‘ 1
g
yeah you could do something similar too pass the ipxe arguments from grub
o
I have experimented with the grub options mentioned by @thousands-action-31843 and that works as expected. An additional option is needed for specifying the harvester.install.iso_url pointing to the iso image location. Thanks for the responses!! ๐Ÿ‘
t
Thanks for the confirmation that this works with the ISO boot, that is good to know for future reference. You can also just put the ISO location in the config YAML.