Handling the Proxmox volumes on rebuild #228
calebsmithdev
started this conversation in
General
Replies: 1 comment
-
It's been a while since I've done a complete rebuild of the cluster, but I think I solved your issue in the 67f160f commit. A Proxmox update probably broke/changed the way API requests are handled, giving errors on UPDATE calls with parameters that aren't used. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
First, your setup has been very inspirational in my own process and has been a huge help as I've been learning k8s and getting them setup in my own Proxmox cluster. I'm still fairly new to a lot of this setup, but I've been doing a lot of tinkering and exploring setting up each component of the build individually.
One of the steps I am struggling with is the Proxmox volumes. I can stand up the full flow in Tofu, and then added some bash scrips for bootstrapping my k8s apps after it's setup. But if I remove the state of the Proxmox volumes on a destroy, then re-add them manually (similar to this https://github.com/vehagn/homelab/blob/main/tofu/kubernetes/bootstrap/volumes/README.md), It's failing to continue the
tofu apply
since the API is returning a different response and wanting to destroy the resource. I know there is aforce_new
on the size, so if I comment that out, then I get an error like the following:How are you getting past this point in the rebuild so it can start creating the k8s persistent volumes?
Beta Was this translation helpful? Give feedback.
All reactions