k8s upgrade changes kube-proxy path

[dpasman]

Bug Report

Upgrading kubernetes version 1.32.x leads to changes in the Proxy hostpath.

@@ -2,7 +2,7 @@
 kind: DaemonSet
 metadata:
   annotations:
-    deprecated.daemonset.template.generation: "1"
+    deprecated.daemonset.template.generation: "2"
   labels:
     k8s-app: kube-proxy
     tier: node
@@ -74,7 +74,7 @@
         operator: Exists
       volumes:
       - hostPath:
-          path: /lib/modules
+          path: /usr/lib/modules
           type: ""
         name: lib-modules
       - hostPath:

 < dry run, change skipped

Description

The above change will be done by running talosctl -n 192.168.1.88 upgrade-k8s --to 1.33.1 --dry-run. I have tried this on multiple clusters but the issue remains on all of them with kube-proxy enabled. Although this could be a change that has to be made to support latest modules, it will break kube-proxy. It leads to a crashloopbackoff which timeouts the upgrade-k8s installation script ran from talosctl leaving the cluster in a state where some resources are upgraded and some are not.

Logs

   Warning  Failed  2m26s (x294 over 65m)  kubelet  (combined from similar events): Error: failed to generate container ""  │
│ spec: failed to apply OCI options: failed to mkdir "/usr/lib/modules": mkdir /usr/lib/modules: read-only file system 

Environment

• Talos version: v1.10.4 (both client and server)
• Kubernetes version: 1.32.0
• Platform: Proxmox VM (?)