KEP-NNNN: CSI Direct In-Memory Environment Variable Injection

[AssafKatz3]

Title: KEP-NNNN: CSI Direct In-Memory Environment Variable Injection

Summary:
This PR introduces the KEP package for CSI Direct In-Memory Environment Variable Injection and requests assignment of a KEP number.

Why this PR:

• Adds KEP package (README, KEP document, ALTERNATIVES, GRADUATION) describing NodeGetEnvVars CSI extension
• Proposes a secure, batched, UDS-based NodeGetEnvVars RPC for low-latency, in-memory environment variable injection
• Includes metrics, test plan, and graduation criteria

Changes requested from reviewers:

• Assign a KEP number and update filenames (replace NNNN)
• SIG-Storage feedback on design and security model
• SIG-Node feedback on kubelet integration and kubelet feature gate semantics
• SIG-Auth review for RBAC and ProviderClass authoring/validation
• Volunteers to review proposed metrics and help craft alerting

Testing / Implementation notes:

• Prototype implementation planned: fork secrets-store-csi-driver and add NodeGetEnvVars support
• Proposed default kubelet RPC timeout: 5s (configurable)

Next steps upon KEP number assignment:

• Replace NNNN in filenames and internal references
• Submit CSI spec PR proposing NodeGetEnvVars and ENV_VAR_INJECTION NodeServiceCapability
• Open a SIG-Storage meeting slot and post to mailing list for review

Files changed:

• README.md — package overview and next steps
• kep.yaml — metadata & metrics
• 0000-csi-direct-env-injection.md — KEP document
• ALTERNATIVES.md — alternatives analysis
• GRADUATION.md — graduation criteria and tests

Maintainers: @AssafKatz (author)

/cc @kubernetes/sig-storage-pr-reviews @kubernetes/sig-node-pr-reviews @kubernetes/sig-auth

[k8s-ci-robot]

@AssafKatz3: GitHub didn't allow me to request PR reviews from the following users: kubernetes/sig-storage-pr-reviews, kubernetes/sig-node-pr-reviews, kubernetes/sig-auth.

Note that only kubernetes members and repo collaborators can review this PR, and authors cannot review their own PRs.

Details

In response to this:

Title: KEP-NNNN: CSI Direct In-Memory Environment Variable Injection

Summary:
This PR introduces the KEP package for CSI Direct In-Memory Environment Variable Injection and requests assignment of a KEP number.

Why this PR:

• Adds KEP package (README, KEP document, ALTERNATIVES, GRADUATION) describing NodeGetEnvVars CSI extension
• Proposes a secure, batched, UDS-based NodeGetEnvVars RPC for low-latency, in-memory environment variable injection
• Includes metrics, test plan, and graduation criteria

Changes requested from reviewers:

• Assign a KEP number and update filenames (replace NNNN)
• SIG-Storage feedback on design and security model
• SIG-Node feedback on kubelet integration and kubelet feature gate semantics
• SIG-Auth review for RBAC and ProviderClass authoring/validation
• Volunteers to review proposed metrics and help craft alerting

Testing / Implementation notes:

• Prototype implementation planned: fork secrets-store-csi-driver and add NodeGetEnvVars support
• Proposed default kubelet RPC timeout: 5s (configurable)

Next steps upon KEP number assignment:

• Replace NNNN in filenames and internal references
• Submit CSI spec PR proposing NodeGetEnvVars and ENV_VAR_INJECTION NodeServiceCapability
• Open a SIG-Storage meeting slot and post to mailing list for review

Files changed:

• README.md — package overview and next steps
• kep.yaml — metadata & metrics
• 0000-csi-direct-env-injection.md — KEP document
• ALTERNATIVES.md — alternatives analysis
• GRADUATION.md — graduation criteria and tests

Maintainers: @AssafKatz (author)

/cc @kubernetes/sig-storage-pr-reviews @kubernetes/sig-node-pr-reviews @kubernetes/sig-auth

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-sigs/prow repository.

[linux-foundation-easycla]

• ❌ The email address for the commit (3541c7a) is not linked to the GitHub account, preventing the EasyCLA check. Consult this Help Article and GitHub Help to resolve. (To view the commit's email address, add .patch at the end of this PR page's URL.) For further assistance with EasyCLA, please submit a support request ticket.

[k8s-ci-robot]

Welcome @AssafKatz3!

It looks like this is your first PR to kubernetes/enhancements 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/enhancements has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: AssafKatz3
Once this PR has been reviewed and has the lgtm label, please assign kikisdeliveryservice for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• keps/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

Hi @AssafKatz3. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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-sigs/prow repository.

[k8s-ci-robot]

@AssafKatz3: Reiterating the mentions to trigger a notification:
@kubernetes/sig-storage-pr-reviews, @kubernetes/sig-node-pr-reviews

Details

In response to this:

Title: KEP-NNNN: CSI Direct In-Memory Environment Variable Injection

Summary:
This PR introduces the KEP package for CSI Direct In-Memory Environment Variable Injection and requests assignment of a KEP number.

Why this PR:

• Adds KEP package (README, KEP document, ALTERNATIVES, GRADUATION) describing NodeGetEnvVars CSI extension
• Proposes a secure, batched, UDS-based NodeGetEnvVars RPC for low-latency, in-memory environment variable injection
• Includes metrics, test plan, and graduation criteria

Changes requested from reviewers:

• Assign a KEP number and update filenames (replace NNNN)
• SIG-Storage feedback on design and security model
• SIG-Node feedback on kubelet integration and kubelet feature gate semantics
• SIG-Auth review for RBAC and ProviderClass authoring/validation
• Volunteers to review proposed metrics and help craft alerting

Testing / Implementation notes:

• Prototype implementation planned: fork secrets-store-csi-driver and add NodeGetEnvVars support
• Proposed default kubelet RPC timeout: 5s (configurable)

Next steps upon KEP number assignment:

• Replace NNNN in filenames and internal references
• Submit CSI spec PR proposing NodeGetEnvVars and ENV_VAR_INJECTION NodeServiceCapability
• Open a SIG-Storage meeting slot and post to mailing list for review

Files changed:

• README.md — package overview and next steps
• kep.yaml — metadata & metrics
• 0000-csi-direct-env-injection.md — KEP document
• ALTERNATIVES.md — alternatives analysis
• GRADUATION.md — graduation criteria and tests

Maintainers: @AssafKatz (author)

/cc @kubernetes/sig-storage-pr-reviews @kubernetes/sig-node-pr-reviews @kubernetes/sig-auth

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-sigs/prow repository.