Automated Install on Proxmox? #6970
Unanswered
Just-Insane
asked this question in
Q&A
Replies: 1 comment 1 reply
-
When #5897 is merged, you should be able to just use host names. In the meantime, I pull the MAC address from the Proxmox VM file and use that to find the IP from dnsmasq, using this script: https://github.com/alexpdp7/alexpdp7/blob/master/personal_infra/playbooks/roles/talos/files/get-ip This playbook is poorly documented, but might serve you as a base: https://github.com/alexpdp7/alexpdp7/tree/master/personal_infra/playbooks/roles/talos (Happy to answer questions about that.) |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am looking to see what would be required to enable a more automated cluster install on Proxmox.
From what I've seen, the options for a more automated install are listed in #4944, and were outlined as:
I am using Terraform to deploy the cluster, however, due to not being able to install the qemu-guest-agent, terraform is not able to get the guest IP from DHCP, which means I have to either look in the console manually or check my DHCP server for leases, and then populate machineconfigs with a static IP and then apply those configs.
It seems like the best path forward would be:
Generate an ISO using the nocloud image, which I can then use Proxmox's cloudinit support to populate static IPs on the nodes and generate machine configs.
An alternative would be to create an image that includes qemu-guest-agent prior to packaging, though I feel like that would be against the principals of the project.
Once the cluster is up, I can use https://github.com/crisobal/qemu-guest-agent-talos to install the agent via a daemonset, but that still leaves me with no way of automating machineconfig deployment from a standard ISO.
Maybe I'm missing something obvious that would make this less complicated?
Beta Was this translation helpful? Give feedback.
All reactions