Relaxed validation for Services names

[adrianmoisey]

Enhancement Description

• One-line enhancement description (can be used as a release note): Relaxed validation for Services names
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-network/5311-relaxed-validation-for-service-names/README.md
• Discussion Link: https://github.com/kubernetes/enhancements/pull/5315
• Primary contact (assignee): @adrianmoisey
• Responsible SIGs: sig-network
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.34
  • Beta release target (x.y): 1.35
  • Stable release target (x.y): 1.36
• [ ] Alpha
  • [ ] KEP (k/enhancements) update PR(s): https://github.com/kubernetes/enhancements/pull/5315
  • [ ] Code (k/k) update PR(s):
  • [ ] Docs (k/website) update PR(s):

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

[adrianmoisey]

/sig network

[adrianmoisey]

/assign

[danwinship]

/milestone v1.34 /label lead-opted-in

Targeting alpha for 1.34

[jenshu]

Hi @adrianmoisey 👋, v1.34 Enhancements team here.

This is a reminder of the upcoming PRR Freeze on Thursday 12th June 2025.

By this date, there must be a PR open in k/enhancements with:

• The KEP's PRR questionnaire filled out.
• The kep.yaml updated with the stage, latest-milestone, and milestone struct filled out.
• A PRR approval file with the PRR approver listed for the stage the KEP is targeting.

Having the PRR questionnaire filled out by this deadline will help ensure that the PRR team has enough time to review your KEP before Enhancements Freeze on Friday 20th June 2025. For more information on the PRR process, see here.

[jenshu]

Hello again @adrianmoisey 👋, v1.34 Enhancements team here.

Just checking in as we approach enhancements freeze on 21:00 UTC Friday 20th June 2025 / 14:00 PST Friday 20th June 2025.

This enhancement is targeting stage alpha for v1.34 (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: v1.34.
• [ ] 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). If your production readiness review is not completed yet, please make sure to fill the production readiness questionnaire in your KEP by the PRR Freeze deadline on Thursday 12th June 2025 so that the PRR team has enough time to review your KEP.

I see that you have a PR open with these changes.

• [ ] In the kep.yaml, you please also update the status to implementable?

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

If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you!

[adrianmoisey]

Hey @jenshu

Thanks for the update.

I believe all those items are now done as my PR has been merged.

[jenshu]

Hi @adrianmoisey,

Thanks for the update. With all the requirements fulfilled, this enhancement is now marked as tracked for the upcoming enhancements freeze 🚀

/label tracked/yes

[graz-dev]

Hi @adrianmoisey 👋 -- this is Graziano (@graz-dev) from the 1.34 Communications Team!

For the 1.34 release, we are currently in the process of collecting and curating a list of potential feature blogs, and we'd love for you to consider writing one for your enhancement!

As you may be aware, feature blogs are a great way to communicate to users about features which fall into (but not limited to) the following categories:

• This introduces some breaking change(s)
• This has significant impacts and/or implications to users
• ...Or this is a long-awaited feature, which would go a long way to cover the journey more in detail 🎉

To opt in to write a feature blog, could you please let us know and open a "Feature Blog placeholder PR" (which can be only a skeleton at first) against the website repository by Friday 11th July? For more information about writing a blog, please find the blog contribution guidelines 📚

[!Tip] Some timeline to keep in mind:

• 02:00 UTC Friday 11th July 2025: Feature blog PR freeze
• Friday 8th August 2025: Feature blogs ready for review
• You can find more in the release document

[!Note] In your placeholder PR, use XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release.

[rashansmith]

Hello @adrianmoisey 👋, 1.34 Docs Shadow here!

Does this enhancement work planned for 1.34 require any new docs or modification to existing docs? If so, please follows the steps here to open a PR against dev-1.34 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday 3rd July 2025 18:00 PDT.

Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.

Thank you!

[rashansmith]

Hello @adrianmoisey 👋, 1.34 Docs Shadow here!

Does this enhancement work planned for 1.34 require any new docs or modification to existing docs? If so, please follows the steps here to open a PR against dev-1.34 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday 3rd July 2025 18:00 PDT.

Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.

Thank you!

Just a reminder to open a placeholder PR against dev-1.34 branch in the k/website repo for this (steps available here) for this KEP if it requires new or modifications to existing docs:

The deadline for this is Thursday July 3 at 18:00 PDT. Thanks! 🚀

[graz-dev]

Hi @adrianmoisey 👋, 1.34 Communications Team here again!

This is a gentle reminder for the feature blog deadline mentioned above, which is 02:00 UTC Friday 11th July 2025. To opt in, please let us know and open a Feature Blog placeholder PR against k/website by the deadline. If you have any questions, please feel free to reach out to us!

[!Tip] Some timeline to keep in mind:

• 02:00 UTC Friday 11th July 2025: Feature blog PR freeze
• Friday 8th August 2025: Feature blogs ready for review
• You can find more in the release document

[!Note] In your placeholder PR, use XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release.

[jenshu]

Hey again @adrianmoisey 👋, v1.34 Enhancements team here.

Just checking in as we approach code freeze and test freeze at 02:00 UTC Friday 25th July 2025 / 19:00 PDT Thursday 24th July 2025.

Here's where this enhancement currently stands:

• [x] All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• [x] All PRs are ready to be merged (they have approved and lgtm labels applied) by the code freeze deadline. This includes tests.

Per the issue description, these are all of the implementation (code-related) PRs for 1.34:

• https://github.com/kubernetes/kubernetes/pull/132339

Please let me know (and keep the issue description updated) if there are any other PRs in k/k that we should track for this KEP, so that we can maintain accurate status.

If the implementation work for this enhancement is occurring out-of-tree (i.e., outside of k/k), please link the relevant PRs in the issue description for visibility. Alternatively, if you're unable to provide specific PR links, a confirmation that all out-of-tree implementation work is complete and merged will help us finalize tracking and maintain accuracy.

This enhancement is now marked as Tracked for code freeze!

[rayandas]

Hi @adrianmoisey :wave:, v1.35 Enhancements Lead here.

I am closing the v1.34 milestone now.

If you'd like to work on this enhancement in v1.35, please have the SIG lead opt-in by adding the lead-opted-in label, which ensures it gets added to the tracking board. Also, please set the milestone to v1.35 using /milestone v1.35.

Thanks!

/remove-label lead-opted-in /remove-label tracked/yes /milestone clear

[adrianmoisey]

/milestone v1.35

@thockin could you do the lead-opted-in label?

EDIT: And I guess the milestone label also

[k8s-ci-robot]

@adrianmoisey: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your Milestone Maintainers Team and have them propose you as an additional delegate for this responsibility.

In response to this:

/milestone v1.35

@thockin could you do the lead-opted-in label?

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.

[danwinship]

/label lead-opted-in /milestone v1.35

targeting beta for 1.35

[musaprg]

@adrianmoisey Hi. I noticed that the feature gate RelaxedServiceNameValidation is not in the Kubernetes document. I've submitted a small PR to update the documentation, but I'm not confident if it's intended description by feature owners. Could you check the PR? If you've already worked on it in another PR, I'll close mine.

https://github.com/kubernetes/website/pull/52447

[adrianmoisey]

Thanks for that. I decided to not write anything in the Kubernetes documentation, I couldn't find any reference who the current validation of Services, so I figured that nothing needed updating. You're welcome to continue work on your PR though, I appreciate the help.

[chanieljdan]

Hello @adrianmoisey 👋, v1.35 Enhancements team here.

This is a reminder of the upcoming PRR freeze on Thursday 9th October 2025 (AoE) / Friday 10th October 2025, 12:00 UTC.

This enhancement is targeting stage beta for v1.35 (correct me, if otherwise)

Here's where this enhancement currently stands:

• [x] PR open or merged with the KEP's PRR questionnaire filled out.
• [x] PR open or merged with kep.yaml updated with the stage, latest-milestone, and milestone struct filled out.
• [x] PR open or merged with a PRR approval file with the PRR approver listed for the stage the KEP is targeting.

Note that the PRs are not required to be approved or merged by the PRR freeze deadline. Having the PRR questionnaire filled out by the deadline will help ensure that the PRR team has enough time to review your KEP before enhancements freeze on Thursday 16th October 2025 (AoE) / Friday 17th October 2025, 12:00 UTC. For more information on the PRR process, see here.

With all the PRR freeze requirements in place, this enhancement is now marked as Tracked for PRR freeze! Please keep the issue description up-to-date with appropriate stages as well.

/label tracked/yes

[chanieljdan]

Hello @adrianmoisey 👋, v1.35 Enhancements team here.

Just checking in as we approach enhancements freeze on Thursday 16th October 2025 (AoE) / Friday 17th October 2025, 12:00 UTC.

This enhancement is targeting stage beta for v1.35 (correct me, if otherwise)

Here's where this enhancement currently stands:

• [x] KEP readme using the latest template has been merged into the k/enhancements repo.
• [x] KEP status is marked as implementable for latest-milestone: v1.35.
• [x] KEP readme has up-to-date graduation criteria.
• [x] 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 update the following:

• Update the stage label to stage/beta to match the intended target stage for 1.35

I'll mark the status of this enhancement to be At risk for enhancements freeze, but the only thing missing here is just updating the label, once updated it can be marked as Tracked!

[aojea]

@chanieljdan I've updated the label from alpha to beta, please let us know if we need something elso are we are good for the freeze

[rayandas]

Thanks @aojea This KEP is now marked as Tracked for Enhancements freeze.

[kernel-kun]

Hello @adrianmoisey :wave:, v1.35 Docs Shadow here.

Does this enhancement work planned for v1.35 require any new docs or modification to existing docs?

If so, please follow the steps here to open a PR against dev-1.35 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday 23th October 2025.

Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.

Thank you!

[SwathiR03]

Hi @adrianmoisey 👋, this is Swathi (@SwathiR03 ) from the 1.35 Communications Team!

For the 1.35 release, we are currently in the process of collecting and curating a list of potential feature blogs, and we'd love for you to consider writing one for your enhancement!

As you may be aware, feature blogs are a great way to communicate to users about features which fall into (but are not limited to) the following categories:

• This introduces some breaking change(s)
• This has significant impacts and/or implications to users
• ...Or this is a long-awaited feature, where the blog would go a long way to cover the journey in more detail 🎉

To opt in to write a feature blog, could you please let us know and open a "Feature Blog placeholder PR" (which can be only a skeleton at first) against the website repository by Friday, the 31st of October? For more information about writing a blog, please find the blog contribution guidelines 📚

[!Tip] Some timelines to keep in mind:

• 12:00 UTC Friday, 31st October: Feature blog PR freeze
• Friday, 21st November: Feature blogs ready for review
• You can find more in the release document

[!Note] In your placeholder PR, use XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release.

[kernel-kun]

Hello @adrianmoisey 👋, this is Tushar Mittal (@kernel-kun) from v1.35 Release Docs team. Thanks for confirming that no Docs update are required for this KEP and reflecting the same within description.

[dipesh-rawat]

Hi @adrianmoisey 👋, v1.35 Release Team shadow here!

From reviewing the KEP-5311 readme (here) and code PR https://github.com/kubernetes/kubernetes/pull/134493, this feature is behind feature gate RelaxedServiceNameValidation which is moving to beta in v1.35. We'll need to ensure this is documented in the feature gate documentation (here). This KEP will need doc udpate for v1.35 release.

For more details, please refer to the documentation here.

[adrianmoisey]

Hi @adrianmoisey 👋, v1.35 Release Team shadow here!

From reviewing the KEP-5311 readme (here) and code PR kubernetes/kubernetes#134493, this feature is behind feature gate RelaxedServiceNameValidation which is moving to beta in v1.35. We'll need to ensure this is documented in the feature gate documentation (here). This KEP will need doc udpate for v1.35 release.

For more details, please refer to the documentation here.

Thanks for pointing that out! Sorry for the miss. I've made https://github.com/kubernetes/website/pull/52920

[SwathiR03]

Hi @adrianmoisey 👋, Swathi(@SwathiR03) from the 1.35 Communications Team here again!

This is a gentle reminder for the feature blog deadline mentioned above, which is 12:00 UTC, Friday, the 31st of October. To opt in, please let us know and open a Feature Blog placeholder PR against k/website by the deadline. If you have any questions, please feel free to reach out to us!

[!Tip] Some timelines to keep in mind:

• 12:00 UTC Friday, 31st October: Feature blog PR freeze
• Friday, 21st November: Feature blogs ready for review
• You can find more in the release document

[!Note] In your placeholder PR, use XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release.

[chanieljdan]

Hey again @adrianmoisey 👋, v1.35 Enhancements team here.

Just checking in as we approach code freeze and test freeze at Thursday 6th November 2025 (AoE) / Friday 7th November 2025, 12:00 UTC.

Here's where this enhancement currently stands:

• [x] All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• [x] All PRs are ready to be merged (they have approved and lgtm labels applied) by the code freeze deadline. This includes tests.

Per the issue description, these are all of the implementation (code-related) PRs for v1.35:

• https://github.com/kubernetes/kubernetes/pull/134493

Please let me know (and keep the issue description updated) if there are any other PRs in k/k that we should track for this KEP, so that we can maintain accurate status.

If the implementation work for this enhancement is occurring out-of-tree (i.e., outside of k/k), please link the relevant PRs in the issue description for visibility. Alternatively, if you're unable to provide specific PR links, a confirmation that all out-of-tree implementation work is complete and merged will help us finalize tracking and maintain accuracy.

This enhancement is now marked as Tracked for code freeze!

Please note that KEPs targeting stable need to have the status field marked as implemented in the kep.yaml file after code PRs are merged.

/label tracked/yes

[kernel-kun]

Hello @adrianmoisey 👋, this is Tushar Mittal (@kernel-kun) from v1.35 Release Docs team.

Please take a look at Documenting for a release - PR Ready for Review to get your Docs PR ready for review before Tuesday 18th November 2025.

Please let us know once your PR is fully Ready for Review — meaning all documentation updates are complete and it’s awaiting reviewer feedback — so we can update our tracking.

Thank you!