HOMELAB-956: feat(talos): raise worker kubelet maxPods to 150 #177
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "plane/HOMELAB-956-kubelet-maxpods"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Bump worker
kubelet.extraConfig.maxPodsfrom the default 110 to 150 via the Talosworker_config_patchlocal in thetalos-clustermodule. Unblocks HOMELAB-954 (WorkAdventure pods Pending due toFailedScheduling / Too many podson wk-01; wk-02 cordoned pending HDD replacement).Apply (Atlantis offline — manual)
Expected plan shape: updates
talos_machine_configuration_apply.worker["prod-wk-01"]and.worker["prod-wk-02"]in place. Talos reloads kubelet without a full node reboot.Verify after apply
Rollback
Revert this commit, re-apply. Kubelet reloads back to default.
wk-01 is capped at the kubelet default (110 pods/node) and, with wk-02 cordoned pending HDD replacement, new deploys (observed on HOMELAB-954 WorkAdventure) hit FailedScheduling / "Too many pods". Raise the cap via the worker config patch so there's headroom for the current stack (harbor, temporal, longhorn, monitoring, etc.) plus new workloads. Adds `kubelet.extraConfig.maxPods = 150` to the worker_config_patch local. Applies to every worker via the existing talos_machine_configuration_apply.worker loop. Talos reloads kubelet in place — no full node reboot. Apply path (Atlantis is offline, manual for now): cd prod/terraform && terraform plan -out=956.tfplan terraform apply 956.tfplan Verify after apply: kubectl get node prod-wk-01 -o jsonpath='{.status.capacity.pods}{"\n"}' # expect: 150 Unblocks HOMELAB-954 (WorkAdventure pods currently Pending).