Welcome @LarytheLord!

It looks like this is your first PR to kubernetes/kubernetes 🎉. 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/kubernetes 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. 😃

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

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

Hi @LarytheLord. 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.

Release-note block has been added (NONE).

Since this is my first PR in kubernetes/kubernetes, could a Kubernetes org member please take a quick look and, if appropriate, run /ok-to-test?

This PR may require API review.

If so, when the changes are ready, complete the pre-review checklist and request an API review.

Status of requested reviews is tracked in the API Review project.

/assign thockin

Quick follow-up for maintainers:

This PR only updates API field descriptions for clarity (no behavior/schema changes). If appropriate, could a Kubernetes org member help with:

• /ok-to-test
• triage/priority labels (/triage accepted, /priority backlog)

I can adjust wording further if preferred.

/approve cancel
/sig api-machinery
/assign liggitt

Small clarifier: this PR is comments-only (no API schema/behavior/defaulting change), and just aligns internal wording with the already-clear external wording for env-from key constraints.

If this looks reasonable, a quick /ok-to-test + /lgtm would unblock it.

/ok-to-test

LGTM label has been added.

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: thockin

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

The pull request process is described here