Helm Chart Does Not Deploy on Talos because of legacy hostPath mount

[joelmccoy]

/kind bug

What happened?
Tried deploying the helm chart on a Talos OS cluster and it fails to come up. The logs indicated it was trying to create the directory as defined here in this volume. Get an error as Talos is a readonly file system and will not allow you to write to /etc*. I manually removed this volume and corresponding mount and the chart came up as expected.

What you expected to happen?
The chart should come up (i.e. this legacy volume mount should be removed) OR the values should expose to be able to disable this volume mount (or at least change the storage type).

How to reproduce it (as minimally and precisely as possible)?
Deploy this chart on a fresh install of Talos

Anything else we need to know?:
Can we either remove this legacy config hostPath? Or can we at least add a value to disable this in the helm chart? I would be happy to toss up a PR for either of those.

Environment

• Kubernetes version (use kubectl version): v1.30.4
• Driver version: 2.0.6
• Chart Version: 3.0.8

Please also attach debug logs to help us better diagnose
Failed event from efs-csi-node pods:

Warning  Failed     52s                kubelet            Error: failed to generate container "bdb5e3bc68e4a5f41fb086fe52bc328e5834b9b1a7b2ef031f28b1dcda1dd0f1" spec: failed to generate spec: failed to mkdir "/etc/amazon/efs": mkdir /etc/amazon: read-only file system

• Instructions to gather debug logs can be found here

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale