Pod not supported on Fargate: invalid SecurityContext fields: Privileged

[anthosz]

/kind bug

What happened?
Unable to use fargate for the efs-csi-controller:

│   Warning  FailedScheduling  11m   fargate-scheduler  Pod not supported on Fargate: invalid SecurityContext fields: Privileged                                                            │

What you expected to happen?
The pod spawn on fargate

How to reproduce it (as minimally and precisely as possible)?
Create a fargate profile
Install the latest helm chart version of efs-csi-driver: 3.0.1

Environment

• Kubernetes version (use kubectl version): 1.29 (EKS)
• Driver version: v2.0.1

[anthosz]

Probably related to #1100

[anthosz]

Workaround found:
Due to the fact deleteAccessPointRootDir is set to false by default, containerSecurityContext.privileged was set to false (seems only used by deleteAccessPointRootDir).

To check if default values.yaml can be aligned (both to true or both to false) in addition of this issue

[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

[k8s-triage-robot]

The Kubernetes project currently lacks enough active 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 rotten
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten