tofu(proxmox): API-only native cloud-init; move node baseline to Ansible node_baseline role
Co-Authored-By: Claude Opus 4.8 <[email protected]>
This commit is contained in:
1 parent
8a8f28bf80
commit
a2392a4a43
10 files changed
+143
-108
No files matched your search
@@ -1,6 +1,14 @@
|
||||
# infra/cloud-init — first-boot baseline templates
|
||||
|
||||
The "Baseline" node lifecycle stage (docs/02 stage 2). `user-data.yaml.tftpl` is
|
||||
> **RETIRED (API-only migration):** the `user-data.yaml.tftpl` snippet was removed
|
||||
> when Proxmox provisioning moved to **API-only native cloud-init**. Custom snippets
|
||||
> require SSH/SFTP to the Proxmox host, which is not reachable here, so bpg's native
|
||||
> `initialization` block now sets only the login user + SSH keys and static IP/DNS
|
||||
> (via the built-in cloud-init API options). The rich first-boot baseline (packages,
|
||||
> kernel modules, Longhorn disk, swap-off) now lives in the Ansible **`node_baseline`
|
||||
> role** (`infra/ansible`), run before k3s. The notes below are historical context.
|
||||
|
||||
The "Baseline" node lifecycle stage (docs/02 stage 2). `user-data.yaml.tftpl` was
|
||||
rendered by OpenTofu (`templatefile()`) and shipped to Proxmox as a **cloud-init
|
||||
user-data snippet** (`proxmox_virtual_environment_file`, one per node), referenced
|
||||
by each VM's `initialization.user_data_file_id`. **Authoring only — never applied.**
|
||||
|
||||
Reference in new issue
Block a user