FYI, you don't really need to set the vmid. If you don't the terraform provider will use the next available VM ID. This makes the terraform scripts a bit more flexible
Thank you for the video, I have been looking for a way to do this as I have been using Proxmox in my home lab and love it! Learned Terraform for my work with AWS and really wanted a way to use it for my home lab as well. Note, that an even better approach for the credentials is to set environment variables `TF_VARS_proxmox_api_token_id` and `TF_VARS_proxmox_api_token_secret` and export them so Terraform picks them up. This way you don't have to worry about accidentally checking that file into a repository by mistake. You can also set them in your shell `rc` file (ie ~/bashrc) so they are always set. Options expand from there. This is what I will probably do.
thanks for making this. i've been using the proxmox terraform provider for some time now to provision my k3s cluster. hopefully this video gets the provider more attention since it is lacking in some functionality and has been buggy in some of my experiences
OK... Christian did it again. I am still confused about how Terraform picks the file names to run plan and build without using -var-file parameter. Also, I did have a very ugly moment (lots of "F" word usage🤣 ) as I didn't notice the wrong network subnet specification (my put "0" instead of 24 🤦♂️). After that Proxmox created a new cloned VM like a champ. THANK YOU Christian. One more - should anyone try to specify Vlan us "tag =" withing the "network" parameter brackets. Took me a while too. Now a suggestion for video for Christian - a short version for using Terraform to create Proxmox LXD container. It should be long hanging fruit as far as RUclips monatiztion is concerned.
It is 4:30 in the morning and just wanted relax and watch some videos … now i that have seen yours and i wanted to get up and try it out. VERY NICE WORK to get me out of my warm and cosy bed 🎉😂 need to remember watching cat videos next time
@@christianlempa 😂😂😂👍 dein Video war interessanter als gedacht. Scriptbasiert eine Test Umgebung aufzusetzen steht schon lange auf meiner Liste. Was ich bisher gemacht/versucht habe mit vagrant und virtual Box war nicht sehr stabil😔
Whooo, this is awesome. Thank you for this video, good job ;) I am also using Packer and Terraform for my VM's. I am also using Argo workflows to rebuild my template every second day so that my template is 100% up-to-date.
To provision a Kubernetes cluster in my Proxmox homelab, it was long and tedious. Before: - I had to create the virtual machines manually from an ISO, - Then I accelerated the process with Cloud-Init images, - But i had to install the packages manually, - Same for the configurations - I make sure to make snapshots of my initial configuration, - If your configuration fails, i delete my machines and we start again... Duration : 15-30 minutes and more.... Now : a Terraform declarative file is enough to get my kubernetes cluster with the desired configuration, Duration : 3 to 5 minutes maximum and a simple "terraform apply" is enough to destroy and rebuild my cluster,
What I don't understand: Why not just use the clone-functionality directly in the GUI? At the moment I can't see the advantage of setting this up in code
Now that i have a base image with cloud-init and a disk size of 16gb, If I want to clone it with terraform and i need to increase the disk size for my kubernetes cluster how can I do it without having the exact same parameter? plus i have issue with "virtio0 - cloud-init drive is already attached at 'ide0'"
"virtio0 - cloud-init drive is already attached at 'ide0'" -> I also get the same error from time to time and I don't know why when it happens. I am using Proxmox 8 so maybe something has changed between releases.
Great video Christian. I’m looking forward to getting up to speed with Packer and Terraform. How are you generating the SSH key for your TF provision script? Is it the same key being used for all VMs?
That's a good question, I think you can simply do that using the package manager, however it only does the minor updates, not the major ones where you have to update the package sources
Did you clone from the template which had cloudint disk attached? I did and it deployed the VM fine took the cloudint settings and all was good. But then if I rerun the terraform apply it always tries to update the VM with removing the cloudint disk. I assume this is because in the plan I didn't define cloudint disk?
I am literally doing the same thing, with libvirt instead of proxmox (I figured out I don't need clustering and many other things proxmox offers). I still have to iron out some connection problems, but things are looking good. For vm images, I skipped packer and found suse's MicroOS images, already shipped with k3s (to build my kubernetes cluster, but theres many other flavours)
I have the exact same settings on the disk block as in Proxmox template. but for some reason, the original disk gets replaced by a new one completely empty of the same size of the original.... I am using: disk { storage = "local" type = "scsi" size = "128G" }
That's how I currently do it because for me, it's just easier to manage everything in a single proxmox-terraform project. But you could also split it into multiple projects.
Having trouble getting the provider working, in this case Telmate terraform-proxmox-provider and provisioner. The video seems to gloss over that important detail. As do the others. Meh..
Nice vid! If I don't pass a password for the user in my .tf files, somehow I can login? I'm using ssh keys, but it keeps prompting my for password, although I have not given any passphrase. Any ideas?
If they are identical you can use "count" to specify how many vms you need; if you need to do some adjustments you can build a list of objects and use "for_each" to iterate the objects; if they are completely different, you ca declare multiple "proxmox_vm_qemu" resources
I use a single Git Repo for my Proxmox VMs in Terraform. And I split the multiple projects into separate .tf files. That's probably not the best way to do it, but the only way I know :D
I'm sorry, but you have to refer to the official docs of Proxmox, which needs the API interface to perform automated actions (which requires API token to authenticate)
I dont See the Advantage... You still have to Set every Parameter (IP etc.) Manually But in a File with an extra Thing. Do it in proxmox is way simpler
I think we need to look at the bigger picture why it’s important to learn IaC instead of just Homelab usage. It’s an important skill in professional IT, and the learning benefit is huge!
“root user has all the privileges” - yes, therefore you should NOT use it in terraform and create another user with ALL NEEDED privileges, not all.
FYI, you don't really need to set the vmid. If you don't the terraform provider will use the next available VM ID. This makes the terraform scripts a bit more flexible
Thanks! Yeah it will pick a random ID. However, I have an organized system there, that's why I defined it, but yes you're right ;)
Thank you for the video, I have been looking for a way to do this as I have been using Proxmox in my home lab and love it! Learned Terraform for my work with AWS and really wanted a way to use it for my home lab as well.
Note, that an even better approach for the credentials is to set environment variables `TF_VARS_proxmox_api_token_id` and `TF_VARS_proxmox_api_token_secret` and export them so Terraform picks them up. This way you don't have to worry about accidentally checking that file into a repository by mistake. You can also set them in your shell `rc` file (ie ~/bashrc) so they are always set. Options expand from there. This is what I will probably do.
Thank you! Great ideas to improve :)
This is for sure something that I want to implement on my proxmox cluster. Thanks for sharing!
You always great videos. You take complicated topics and make it understandable.
I appreciate that! Thank you so much
Liked, subbed, and leaving a comment for the algorithm. Appreciate the content - great job.
Did the same kind of thing in Ansible, and now trying to see if I can make a custom Crossplane provider for it.
Automation is awesome!
I'm glad i found this video.
Thank you! :)
thanks for making this. i've been using the proxmox terraform provider for some time now to provision my k3s cluster. hopefully this video gets the provider more attention since it is lacking in some functionality and has been buggy in some of my experiences
What would you rate the provider's current usability from 1-10?
OK... Christian did it again. I am still confused about how Terraform picks the file names to run plan and build without using -var-file parameter. Also, I did have a very ugly moment (lots of "F" word usage🤣 ) as I didn't notice the wrong network subnet specification (my put "0" instead of 24 🤦♂️). After that Proxmox created a new cloned VM like a champ.
THANK YOU Christian. One more - should anyone try to specify Vlan us "tag =" withing the "network" parameter brackets. Took me a while too.
Now a suggestion for video for Christian - a short version for using Terraform to create Proxmox LXD container. It should be long hanging fruit as far as RUclips monatiztion is concerned.
Thanks bro :) great you could solve these issues! Still have other stuff on my list but maybe I'll take a look at LXC at some point 😀
Excellent tutorial, thanks a lot ! Very well explained and you make it look so simple, good work !
It is 4:30 in the morning and just wanted relax and watch some videos … now i that have seen yours and i wanted to get up and try it out. VERY NICE WORK to get me out of my warm and cosy bed 🎉😂 need to remember watching cat videos next time
Haha thank you ;) Glad you enjoyed the video so much you even skipped the cat videos
@@christianlempa 😂😂😂👍 dein Video war interessanter als gedacht. Scriptbasiert eine Test Umgebung aufzusetzen steht schon lange auf meiner Liste. Was ich bisher gemacht/versucht habe mit vagrant und virtual Box war nicht sehr stabil😔
Thanks bro your videos are always informative 🔥🔥🔥
Thank you! Glad you liked it 🙂
Nice work! Keep it up bro.
Thanks, will do!
This is gold! Thanks for sharing.
Thanks 😉
Whooo, this is awesome. Thank you for this video, good job ;)
I am also using Packer and Terraform for my VM's. I am also using Argo workflows to rebuild my template every second day so that my template is 100% up-to-date.
thanks for the demo and info, have a great day
Thanks, you too!
Thanks Christian. I hope life is going well for you.
Thanks mate! Yeah it's all good, thanks for asking 😀
Great tutorial, thanks.
This video came just at the right time. I am planning on doing sth. with that in the next few weeks. Thanks / Danke & Grüße
Vielen Dank! Grüße zurück :)
To provision a Kubernetes cluster in my Proxmox homelab, it was long and tedious.
Before:
- I had to create the virtual machines manually from an ISO,
- Then I accelerated the process with Cloud-Init images,
- But i had to install the packages manually,
- Same for the configurations
- I make sure to make snapshots of my initial configuration,
- If your configuration fails, i delete my machines and we start again...
Duration : 15-30 minutes and more....
Now : a Terraform declarative file is enough to get my kubernetes cluster with the desired configuration,
Duration : 3 to 5 minutes maximum and a simple "terraform apply" is enough to destroy and rebuild my cluster,
Amazing!
What I don't understand: Why not just use the clone-functionality directly in the GUI? At the moment I can't see the advantage of setting this up in code
Have you used the Telmate Proxmox provider to install packages or run scripts on newly built virtual machines without using provisioning?
Now that i have a base image with cloud-init and a disk size of 16gb, If I want to clone it with terraform and i need to increase the disk size for my kubernetes cluster how can I do it without having the exact same parameter? plus i have issue with "virtio0 - cloud-init drive is already attached at 'ide0'"
"virtio0 - cloud-init drive is already attached at 'ide0'" -> I also get the same error from time to time and I don't know why when it happens. I am using Proxmox 8 so maybe something has changed between releases.
Great video Christian. I’m looking forward to getting up to speed with Packer and Terraform.
How are you generating the SSH key for your TF provision script? Is it the same key being used for all VMs?
did you find a solution for this please ?
Great video! Keep it up dude!
Thanks! I'll do
Hi Christian, great video. I am wondering if it is possible to automate Proxmox servers upgrades, not just VMs. Couldn't find a proper playbook
That's a good question, I think you can simply do that using the package manager, however it only does the minor updates, not the major ones where you have to update the package sources
Did you clone from the template which had cloudint disk attached?
I did and it deployed the VM fine took the cloudint settings and all was good.
But then if I rerun the terraform apply it always tries to update the VM with removing the cloudint disk.
I assume this is because in the plan I didn't define cloudint disk?
I am literally doing the same thing, with libvirt instead of proxmox (I figured out I don't need clustering and many other things proxmox offers). I still have to iron out some connection problems, but things are looking good. For vm images, I skipped packer and found suse's MicroOS images, already shipped with k3s (to build my kubernetes cluster, but theres many other flavours)
I had to add "-var-file=credentails.tfvars" whenever running terraform plan or terraform apply, is there something missed?
The file name must end in `.auto.tfvars` in order for Terraform to automatically use it. You appear to have left out the `auto` part.
@@JamesGreen-gv4ynAh perfect thank you!
Amazing... thank you.
You’re welcome
Thanks!
Thank you so much for your support :)
Any way to automate linked clone as its only creating a full clone...
Hi, I followed everything OK. but my VM doesn't pick up the static IP until after I manually reboot it. are you having the same issue?
Do you have an alternative Terraform provider for Proxmox VE 8? Telmate no longer maintains it.
Hi Christian, thanks for your video! Is this provider still up-to-date?
I follow your setup but still this appears>> Error: invalid character '
I have the exact same settings on the disk block as in Proxmox template. but for some reason, the original disk gets replaced by a new one completely empty of the same size of the original....
I am using:
disk {
storage = "local"
type = "scsi"
size = "128G"
}
whats the name of your vscode color theme?
The cloned VM hostname and IP address doesn't change, any idea why this is happening? (retains same hostname and ip as template)
No idea, maybe you could join our discord, share your files and we might be able to help
still waiting for Ansible version of this video... ;)
can i make the new vm have different storage size than the parent vm?
noice
Can you make a video of how to use the username and password instead of the API token and Api secret, I keep getting errors
Any plans to add Ansible to this would be awesome.
Hi, im wondering how to use this in production. Do you just have 1 project where you manage all your virtual mashines from?
That's how I currently do it because for me, it's just easier to manage everything in a single proxmox-terraform project. But you could also split it into multiple projects.
Having trouble getting the provider working, in this case Telmate terraform-proxmox-provider and provisioner. The video seems to gloss over that important detail. As do the others. Meh..
I set a password with cipassword under ciuser, and i can login with those credentials, ani hints?
Nice vid! If I don't pass a password for the user in my .tf files, somehow I can login? I'm using ssh keys, but it keeps prompting my for password, although I have not given any passphrase. Any ideas?
Great video, thank you. How would you change this project to create/maintain a list of vms?
If they are identical you can use "count" to specify how many vms you need; if you need to do some adjustments you can build a list of objects and use "for_each" to iterate the objects; if they are completely different, you ca declare multiple "proxmox_vm_qemu" resources
I use a single Git Repo for my Proxmox VMs in Terraform. And I split the multiple projects into separate .tf files. That's probably not the best way to do it, but the only way I know :D
not working for me
Does anyone know how to use the username and password for Proxmox to deploy instead of using the token and secret?
Please it's urgent
I'm sorry, but you have to refer to the official docs of Proxmox, which needs the API interface to perform automated actions (which requires API token to authenticate)
@@christianlempa is there a way I could text you privately?
Gru
crash for me......
I dont See the Advantage... You still have to Set every Parameter (IP etc.) Manually But in a File with an extra Thing. Do it in proxmox is way simpler
I think we need to look at the bigger picture why it’s important to learn IaC instead of just Homelab usage. It’s an important skill in professional IT, and the learning benefit is huge!
learning another language for what? isn't any better graphical alternative?