Relaxed DNS search string validation

[sethev]

Enhancement Description

• One-line enhancement description (can be used as a release note): Support relaxed validation of DNS search strings
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/4427-relaxed-dns-search-validation
• Discussion Link: https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/4427-relaxed-dns-search-validation
• Primary contact (assignee): @sethev @adrianmoisey
• Responsible SIGs: sig-network
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.32
  • Beta release target (x.y): 1.33
  • Stable release target (x.y): 1.34
• Alpha
  • KEP (k/enhancements) update PR(s):
    • KEP-4427: Relaxed DNS search validation: Initial draft #4428
    • KEP-4427: Add additional DNS search validation relaxation  #4755
    • KEP-4427: Update status of KEP #4884
  • Code (k/k) update PR(s): KEP-4427 : AllowRelaxedDNSSearchValidation kubernetes#127167
  • Docs (k/website) update PR(s):
• Beta
  • KEP (k/enhancements) update PR(s):
    • KEP-4427: Relaxed DNS search validation to beta #5045
    • KEP-4427: Updates required for Beta #5137
  • Code (k/k) update PR(s):
    • Bump KEP-4427 : AllowRelaxedDNSSearchValidation to Beta kubernetes#130128
  • Docs (k/website) update(s):

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

[sethev]

/sig network

[jpbetz]

/milestone v1.30

[jpbetz]

@thockin This one needs /label lead-opted-in

[AnaMMedina21]

Hello @sethev 👋, Enhancements team here.

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

This enhancement is targeting for stage <insert-stage-here> for v1.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: v1.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 update the following:

• Please update kep.yaml, KEP status needs to be marked as implementable
• Can you also update your issue description to link to the KEP? https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/4427-relaxed-dns-search-validation

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!

[sethev]

@AnaMMedina21 working on the implementable field (#4493)

Does the description update look ok?

[AnaMMedina21]

@sethev Looks great! Will keep an eye out for #4493

[sethev]

@AnaMMedina21 status set to implementable!

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

This is targeting alpha for v1.30

[meganwolf0]

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

[chanieljdan]

Hi @sethev @thockin 👋, 1.30 Docs Shadow here.

Does this enhancement work planned for 1.30 require any new docs or modification to existing docs?
If so, please follows the steps here to open a PR against dev-1.30 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday February 22nd 2024 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!

[a-mccarthy]

Hi @thockin and @sethev,

👋 from the v1.30 Communications Team! We'd love for you to opt in to write a feature blog about your enhancement!

We encourage blogs for features including, but not limited to: breaking changes, features and changes important to our users, and features that have been in progress for a long time and are graduating.

To opt in, you need to open a Feature Blog placeholder PR against the website repository.
The placeholder PR deadline is 27th February, 2024.
Here's the 1.30 Release Calendar

[chanieljdan]

Hi @sethev @thockin 👋, 1.30 Docs Shadow here.

Does this enhancement work planned for 1.30 require any new docs or modification to existing docs? If so, please follows the steps here to open a PR against dev-1.30 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday February 22nd 2024 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!

Hi @sethev @thockin 👋, could you review the above before the placeholder deadline tonight? Thanks!

[sethev]

@chanieljdan opened a place holder here: kubernetes/website#45299

[AnaMMedina21]

Hey again @sethev 👋 Enhancements team here,

Just checking in as we approach code freeze at 02:00 UTC Wednesday 6th March 2024 .

Here's where this enhancement currently stands:

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

Also, please let me know if there are other PRs in k/k we should be tracking for this KEP.
As always, we are here to help if any questions come up. Thanks!

[sethev]

@AnaMMedina21 i should have a PR submitted tomorrow, but it looks like i've missed the code freeze for 1.30 :(

[drewhagen]

👋 Hello @sethev

‼️ This KEP needs documentation with a review complete by Doc Freeze on March 26th 18:00 PT (coming up quick!) to get this into the release. After that date, an exception needs to be filed and may risk this feature not getting released with 1.30.

The start of a review was due a week ago, and I see that the documentation is still a draft. Both SIG-Docs and a technical reviewer from SIG network needs to review documentation by that March 26th date.

As a user of Kubernetes, I really appreciate your contribution with good documentation to help me understand how to utilize your new enhancement. Thanks!

[danwinship]

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

targeting beta for 1.33

[fykaa]

Hello @adrianmoisey @jpbetz @thockin 👋, v1.33 Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 14th February 2025 / 19:00 PDT Thursday 13th February 2025.

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

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.33.
• 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 6th February 2025 so that the PRR team has enough time to review your KEP.

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

• status in the kep.yaml should be marked as implementable until stable work has been merged and the feature gates are removed. Please update to implementable
• Please Update the README to include Non-Goals

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 @fykaa

I have updated both of those in #5137
I've also updated the description of this issue updated reflecting that.

Is there anything else needed?

[adrianmoisey]

Hey @fykaa ,

Is all in order for this KEP?

[dipesh-rawat]

Hello @adrianmoisey 👋, 1.33 Enhancements team here.

Now that PR #5137 has been merged, all the KEP requirements are in place and merged into k/enhancements, this enhancement is all good for the upcoming enhancements freeze. 🚀

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

/label tracked/yes

[hacktivist123]

Hello @adrianmoisey 👋, v1.33 Docs Shadow here.

Does this enhancement work planned for v1.33 require any new docs or modification to existing docs?
If so, please follow the steps here to open a PR against dev-1.33 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday 27th February 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!

[rayandas]

Hi @adrianmoisey 👋 v1.33 Docs Lead here.

The deadline to raise a placeholder Docs PR is Thursday 27th February 2025 18:00 PDT.
If this enhancement work requires any new docs or modification to existing docs, please create a placeholder PR (it can be a draft PR for now) before the deadline.

Thanks!

[adrianmoisey]

No documentation updated required, thanks for the checking

[rayandas]

Thanks for the update.

[rytswd]

Hi @adrianmoisey 👋 -- this is Ryota (@rytswd) from the 1.33 Communications Team!

For the 1.33 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 Wednesday, 5th March, 2025? For more information about writing a blog, please find the blog contribution guidelines 📚

Tip

Some timeline to keep in mind:

• 02:00 UTC Wednesday, 5th March, 2025: Feature blog PR freeze
• Monday, 7th April, 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.

[fykaa]

Hey again @adrianmoisey @jpbetz @thockin 👋, v1.33 Enhancements team here,

Just checking in as we approach Code Freeze at 02:00 UTC Friday 21st March 2025 / 19:00 PDT Thursday 20th March 2025.

Here's where this enhancement currently stands:

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

For this enhancement, I couldn’t find any PR listed in the GitHub issue, neither can I find any associated PRs in kubernetes/kubernetes--could you please share the list of PRs that need tracking?

1. Please list the PRs that need to be merged before code freeze
2. Please Update the Issue description to include all the related PRs of this KEP

If you anticipate missing code freeze, you can file an exception request in advance.
Also, please let me know if there are other PRs in k/k we should be tracking for this KEP.

The status of this enhancement is marked as At risk for code freeze.

As always, we are here to help if any questions come up. Thanks!

[rytswd]

Hi @adrianmoisey 👋, 1.33 Communications Team here again!

This is a gentle reminder for the feature blog deadline mentioned above, which is 02:00 UTC Wednesday, 5th March, 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 Wednesday, 5th March, 2025: Feature blog PR freeze
• Monday, 7th April, 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.

[fykaa]

Hello @adrianmoisey @jpbetz @thockin 👋, v1.33 Enhancements team here again.

With all the implementation (code-related) PRs merged per the issue description:

• Bump KEP-4427 : AllowRelaxedDNSSearchValidation to Beta kubernetes#130128

This enhancement is now marked as Tracked for code freeze for the v1.33 Code Freeze!

Additionally, please let me know if there are any other PRs in k/k that we should track for this KEP, so that we can maintain accurate status.