Cluster

1. Drain the Node Draining a node ensures that workloads are safely evicted before cleaning its configuration: kubectl drain <node-name> --ignore-daemonsets --delete-emptydir-data Notes --ignore-daemonsets: Ensures that DaemonSet pods are not deleted. --delete-emptydir-data: Deletes data in emptyDir volumes. ⚠️ Warning: If the node is a control plane node, use --force with caution. 2. Remove the Node from the Cluster To remove the node from the cluster, run: kubectl delete node <node-name> This will delete the node’s representation in the Kubernetes API. ...

Client machine Talos nodes have no shell at all, so you would need some box to run configuration commands. In this case I’m using Ubuntu 22.04 LTS for console to run commands, configuring Talos 1.91 # install TalosCTL, KubeCTL, Helm curl -sL https://talos.dev/install | sh snap install kubectl --classic snap install helm --classic helm repo update Note controlplane (master) node IP and save to variable as well as some other staff ...

For simplicity, this guide uses a flat cluster configuration where each node acts as both a master (control-plane) and a worker. ProxMox Hardware Configuration When setting up ProxMox for Talos Kubernetes nodes, follow these instructions to configure the virtual machine: Memory: Allocate at least 3 GB of RAM per node to ensure smooth operation of the Kubernetes components. Processors: Set the CPU configuration to 2 cores (1 socket, 2 cores). ...