Spaces/colons in access point tags

[Deepercreeper]

/kind bug

What happened? The aws-efs-csi-driver controller fails to parse given tags for access points logging: E0613 13:04:49.293878 1 driver.go:144] Failed to parse input tag string: Key with spaces:value

What you expected to happen? Since spaces are supported by the AWS tagging API (including EFS) tags with spaces should be supported by the aws-efs-csi-driver controller as well.

How to reproduce it (as minimally and precisely as possible)? Deploy the aws-efs-csi-driver helm chart passing the following values:

controller:
  tags:
    key with spaces: value

Anything else we need to know?: This goes for keys and values of tags. The same goes for the colon (:) as part of tag values as it is used to separate key and value when passing the command line argument to the controller pod.

Environment

• Kubernetes version (use kubectl version): 1.29
• Driver version: 2.0.3 (helm chart version 3.0.4)

Please also attach debug logs to help us better diagnose aws-efs-csi-driver.txt

• 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