Allow almost all printable ASCII characters in environment variables

[HirazawaUi]

Enhancement Description

• One-line enhancement description (can be used as a release note): Allow special characters in environment variables
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/4369-allow-special-characters-environment-variable/README.md
• Discussion Link: Environment variables containing colon not allowed kubernetes#53201
• Primary contact (assignee): @HirazawaUi
• Responsible SIGs:
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.30
  • Beta release target (x.y): 1.32
  • Stable release target (x.y): 1.34
• Alpha
  • KEP (k/enhancements) update PR(s):
    • Allow almost all printable ASCII characters in environment variables #4373
    • KEP-4396: promote kep into implementable #4482
  • Code (k/k) update PR(s):
    • Allow almost all printable ASCII characters in environment variables kubernetes#123385
  • Docs (k/website) update PR(s):
    • Document option to allow almost all printable ASCII characters in environment variables website#45125
• Beta
  • KEP (k/enhancements) update PR(s):
    • KEP-4369: Promote to beta (allow ~all ASCII characters in env vars) #4805
  • Code (k/k) update PR(s):
    • KEP-4369: promote RelaxedEnvironmentVariableValidation feature gate to beta kubernetes#126897
  • Docs (k/website) update(s):
    • Promote RelaxedEnvironmentVariableValidation to beta website#47663
• Stable
  • KEP (k/enhancements) update PR(s):
    • KEP-4369: Promote to GA (allow ~all ASCII characters in env vars) #5364
  • Code (k/k) update PR(s):
    • [KEP-4369]: Graduate RelaxedEnvironmentVariableValidation to GA kubernetes#132054
  • Docs (k/website) update(s):
    • Add documentation for graduating the RelaxedEnvironmentVariableValidation to GA. website#51416

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

[kikisdeliveryservice]

@HirazawaUi Can you check and find out which sig will be owning this enhancement and update this issue.

[HirazawaUi]

@HirazawaUi Can you check and find out which sig will be owning this enhancement and update this issue.

I think it should be sig-node

[HirazawaUi]

/sig node
/sig api-machinery
/cc @liggitt @thockin

[thockin]

Agree sig-node

[tjons]

Hello @HirazawaUi 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on Friday, February 9th, 2024 at 02:00 UTC.

This enhancement is targeting for stage alpha for 1.30 (correct me, if otherwise)

Here's where this enhancement currently stands:

• KEP readme using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: 1.30. KEPs targeting stable will need to be marked as implemented after code PRs are merged and the feature gates are removed.
• KEP readme has up-to-date graduation criteria
• KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here).

For this KEP, we would just need to complete the following:

• Merge the KEP readme into the k/enhancements repo.
• Complete the PRR review process and merge it into k/enhancements.
• Mark this KEP as implementable for latest-milestone: 1.30.

The status of this enhancement is marked as at risk for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

[HirazawaUi]

The status of this enhancement is marked as at risk for enhancement freeze

I will try to finish it.