EKS addon: Support priorityClassName configuration for secrets-store-csi-driver dependent chart

[deepakbshetty]

Description

The EKS add-on for Secrets Store CSI Driver AWS does not currently expose configuration options for Secrets Store CSI Driver.

• priorityClassName

These options are already available in the underlying (dependent) Helm chart used by the add-on but are not exposed through the EKS add-on configuration.

Issue

On smaller instance types, the lack of a priorityClassName can cause CSI driver pods to be deprioritized and fail to schedule ahead of other workloads, impacting reliable secret mounting.

Proposed Change

Expose priorityClassName under the secrets-store-csi-driver section of the add-on configuration schema, mapping directly to values already supported by the dependent Helm chart.

Example:

{
  "secrets-store-csi-driver": {
    "priorityClassName": ""
  }
}

---

[alfredocambera-changeorg]

Im also facing this same issue. I got pods not being able to schedule after upgrading to 1.34. I had to patch the daemonset, but it isn't a long term solution

[voronin-ilya]

Until this is fixed, the following configuration works as a workaround (tested on v3.1.1-eksbuild.1):

{
  "secrets-store-csi-driver": {
    "linux": {
      "priorityClassName": "system-node-critical"
    },
    "windows": {
      "priorityClassName": "system-node-critical"
    }
  }
}