k3s version v1.27 installed using https://get.k3s.io making running pod's /tmp as read only after ndoe restart

[nsimha73]

Environmental Info:
K3s Version: v1.127
k3s version v1.27.15+k3s1 (3ced503)
go version go1.21.11

Node(s) CPU architecture, OS, and Version:

Linux stream9-node-1 5.14.0-496.el9.x86_64 #1 SMP PREEMPT_DYNAMIC Mon Aug 12 20:37:54 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Cluster Configuration:
2 nodes cluster with one master

Describe the bug:
On k3s 2 nodes cluster on CentOS stream9 OS, when we deploy helm charts all pods starts running without any issue ( most of our pods are running springboot services ) which are using /tmp of the container file system, once the kubernetes node restarts we are seeing the pod /tmp folder permissions are changed and pod fails to come up as the springboot service try to access /tmp to create files on start.

We would like to know if there are any issues reported like these.