removed netcat dependency with /dev/tcp #2

Merged

kasun merged 5 commits from bug/fix-missing-dependencies-k8s-bootstrap into main

2026-05-31 18:33:17 +02:00

Author	SHA1	Message	Date
kasun	5ac4cb592c	fix: removed failing propagation. will add it later Deploy k8s Bootstrap / Pulumi Preview (pull_request) Successful in 33s Details Deploy k8s Bootstrap / Bootstrap k3s Cluster (pull_request) Has been skipped Details Deploy Proxmox Infra / Pulumi Preview (pull_request) Successful in 42s Details Deploy Proxmox Infra / Pulumi Deploy (pull_request) Has been skipped Details	2026-05-30 19:53:04 +02:00
kasun	980e24c606	fix: added missing sudo Deploy k8s Bootstrap / Pulumi Preview (pull_request) Successful in 38s Details Deploy k8s Bootstrap / Bootstrap k3s Cluster (pull_request) Has been skipped Details	2026-05-30 19:35:37 +02:00
kasun	2f6635aa73	fix: added sudo to kubectl commands Deploy k8s Bootstrap / Pulumi Preview (pull_request) Successful in 31s Details Deploy k8s Bootstrap / Bootstrap k3s Cluster (pull_request) Has been skipped Details	2026-05-30 19:16:36 +02:00
kasun	7212e0e3ef	fix: add triggers and --node-name to k8s-bootstrap commands Without triggers, commands cached in Pulumi state don't re-run when VMs are deleted and recreated with new IDs. This caused stale state where start/install commands were skipped while the new VMs were never bootstrapped, leading to SSH "no route to host" failures. All command resources now carry triggers: [vmId] so they are automatically replaced (and re-run) whenever the underlying VM changes. Also adds --node-name to every k3s install/join command so nodes register under the expected name (k3s-master-1 etc.) regardless of the VM's actual hostname, which cloud-init does not set explicitly.	2026-05-30 19:06:11 +02:00
kasun	e9765bb073	removed netcat dependency with /dev/tcp Deploy k8s Bootstrap / Pulumi Preview (pull_request) Successful in 41s Details Deploy k8s Bootstrap / Bootstrap k3s Cluster (pull_request) Has been skipped Details	2026-05-30 17:24:49 +02:00