configmapGenerator fails to include files containing valid UTF-8 with control characters

[mpol]

What happened?

Trying to include a valid UTF-8 file containing a control character (eg. \u0093) in a config map results in an error during kustomize build.

What did you expect to happen?

A config map containing the file data with the control character correctly escaped or represented using binaryData.

How can we reproduce it (as minimally and precisely as possible)?

# kustomization.yaml
apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization
configMapGenerator:
- files:
  - cfile
  name: cmap

# createcfile.sh
#!/bin/bash
echo $'\xc2\x93' > cfile

Expected output

No response

Actual output

$ kustomize build
Error: map[string]interface {}{"apiVersion":"v1", "data":map[string]interface {}{"cfile":"\u0093\n"}, "kind":"ConfigMap", "metadata":map[string]interface {}{"name":"cmap-bdtdtb6f2c"}}: yaml: control characters are not allowed

Kustomize version

v5.0.1

Operating system

Linux

[k8s-ci-robot]

This issue is currently awaiting triage.

SIG CLI takes a lead on issue triage for this repo, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[natasha41575]

/assign @varshaprasad96

[k8s-triage-robot]

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

[mpol]

Bug still present in 5.4.1.