Expanded DNS configuration

[gjkim42]

Enhancement Description

• One-line enhancement description (can be used as a release note): Allow kubernetes to have expanded DNS(Domain Name System) configuration.
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/2595-expanded-dns-config
• Discussion Link: Prepare to relax the constraints of PodDNSConfig kubernetes#100583
• Primary contact (assignee): @gjkim42
• Responsible SIGs: sig-network
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.22
  • Beta release target (x.y): 1.26
  • Stable release target (x.y): 1.28
• Alpha
  • KEP (k/enhancements) update PR(s): Add expanded DNS configuration KEP #2596
  • Code (k/k) update PR(s): Add feature gate ExpandedDNSConfig kubernetes#100651
  • Docs (k/website) update PR(s): Add ExpandedDNSConfig feature gate website#28096
• Beta
  • KEP (k/enhancements) update PR(s): KEP-2595: Promote to the beta stage #2884
  • Code (k/k) update PR(s): Promote ExpandedDNSConfig feature to beta stage kubernetes#112824
  • Docs (k/website) update(s): Add DNS search domain list limits and remove resolved DNS issue website#37364
• Stable
  • KEP (k/enhancements) update PR(s): KEP-2595: Promote to the GA stage #3914
  • Code (k/k) update PR(s): Promote ExpandedDNSConfig feature to the GA stage kubernetes#116741
  • Docs (k/website) update(s): Update ExpandedDNSConfig docs for GA website#40639

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

[gjkim42]

/sig network

[JamesLaverack]

/milestone v1.22
/stage alpha

[gracenng]

Hi @gjkim42 👋 1.22 Enhancement shadow here.

This enhancement is in good shape, a minor change request in light of Enhancement Freeze on Thursday May 13th:

• Graduation criteria for alpha is incomplete

Thanks!

[gracenng]

Hi @gjkim42 👋 1.22 Enhancements shadow here.
I just wanted to double check to see if SIG-Network will need to do anything for this enhancement and if so, are they OK with it?
Thanks!

[gjkim42]

Hi @gracenng
Updated graduation criteria for alpha.
The Enhancement PR was just merged yesterday with the sig-network's approval.
I think it seems to be OK as it is now.

Thanks :)

[gracenng]

Hi @gjkim42 🌞 1.22 enhancements shadow here.

In light of Code Freeze on July 8th, this enhancement current status is tracked and we are tracking kubernetes/kubernetes#100651.
Please let me know if there is other code PR associated with this enhancement.

Thanks

[gjkim42]

Hi @gracenng

Please let me know if there is other code PR associated with this enhancement.

There isn't. All works for this release has been completed.

Thanks :)

[thockin]

For the record: it sounds like we're waiting for runtimes to implement, so no advancement for 1.23, right?

[gjkim42]

Right. We should wait for container runtimes to support this feature.

Will discuss about the beta promotion later.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[gjkim42]

/remove-lifecycle stale

[thockin]

We did not queue this up for 1.24, so I will tag for 25 and we can re-evaluate then

[Atharva-Shinde]

From what I have seen, ultimately when an enhancement is released out as GA it needs to lock its Feature Gates (before Code Freeze) and set the status to implemented which happens after it has been successfully tracked the release cycle it has opted-in (in this case v1.28).

Tagging the PRR approver for this enhancement @johnbelamaric for a decision.

[enj]

@Atharva-Shinde not sure I see any issues here - all the work for this KEP is already complete, so it is implemented.

[enj]

which happens after it has been successfully tracked the release cycle it has opted-in (in this case v1.28)

Nothing prevents the work from being completed in between code thaw and enhancements freeze (which is what happened here).

[Atharva-Shinde]

Nothing prevents the work from being completed in between code thaw and enhancements freeze (which is what happened here).

Yes I agree on that. It's just the case of changing the status to implementable rather than implemented for now.

[gjkim42]

@Atharva-Shinde

I understand that I should have not updated the status to implemented if all work had not been done.
However, all the work has been done now. Do we need to update the KEP status to implementable and update it back to implemented?

(Please correct me, if I misunderstand something.)

[Atharva-Shinde]

With everything already done for this enhancement, I am leaning towards approving this KEP and getting it tracked. But there is an instance where the enhancement owner had to close the PR which was changing the status to implemented because it should be changed to implemented only after the release is out. I'll ping the PRR team on slack for a decision.

[Atharva-Shinde]

Marking the status of this enhancement as tracked🚀

[Atharva-Shinde]

Hey again @gjkim42 👋

Just checking in as we approach Code freeze at 01:00 UTC Friday, 19th July 2023 .

Here’s the enhancement’s state for the upcoming code freeze:

• All the PRs that are related to your enhancement are linked in the above issue description (for tracking purposes). This includes code, tests, and documentation related PR/s.
• All code related PR/s are merged or are in merge-ready state ( i.e they have approved and lgtm labels applied) by the code freeze deadline. This includes any tests related PR/s too.

This the code related PR/s that I found on this KEP issue:

• Promote ExpandedDNSConfig feature to the GA stage kubernetes#116741

Please keep the issue description up-to-date with all the PR/s that are associated with this KEP and let me know if there are other PR/s in k/k we should be tracking for this KEP.

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

[Atharva-Shinde]

Hey @gjkim42 👋 Enhancements Lead here,
With kubernetes/kubernetes#116741 merged as per the issue description, this enhancement is now tracked for v1.28 Code Freeze. Thanks!

[npolshakova]

Hey @gjkim42 👋 1.29 Enhancements Lead here, is there any more work planned for this KEP? Also is the milestone accurate (are you targeting v1.30 instead of v1.29?)

[gjkim42]

This is already in GA, we have to remove the feature gate in v1.30.

[npolshakova]

Great! I'm going to remove the lead-opted-in label for now. Feel free to add it again once the v1.30 release cycle starts.

/remove-label lead-opted-in

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[salehsedghpour]

/milestone clear