Autopath for Cluster DNS

[prameshj]

Enhancement Description

• One-line enhancement description (can be used as a release note): Support server-side autopath for ClusterDNS
• Kubernetes Enhancement Proposal: Add a KEP for DNS Autopath in pod API #967
• Discussion Link:
• Primary contact (assignee): prameshj
• Responsible SIGs: sig-network
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y) TBD

[prameshj]

/sig network

[kikisdeliveryservice]

Hi @prameshj

Enhancements Lead here. If you could please update your KEP to use the new format that would be great!

Also are you planning on working on this for 1.20? If so, by Enhancements Freeze October 6th:

• The KEP must be merged in an implementable state
• The KEP must have test plans
• The KEP must have graduation criteria.

Best,
Kirsten

[prameshj]

Hi Kirsten, I am working on the new format now. I will be pushing an update to the PR by end of week or sooner. I plan on working on it for 1.20.

[kikisdeliveryservice]

Great! Thanks for the update @prameshj !

/milestone v1.20

[mikejoh]

Hi @prameshj 👋!

I'm one of the Enhancement lead shadows for the 1.20 release cycle. This is a friendly reminder that the Enhancement freeze is on the 6th of October. I'm repeating the requirements needed by then:

• The KEP must be merged in an implementable state.
  • It's provisional at the moment and it's clear that it's worked on!
• The KEP must have test plans.
  • Looks like that is covered.
• The KEP must have graduation criteria.
  • This section is missing in the KEP!

Awesome that you changed to the new KEP template and structure.

Thanks!

[mikejoh]

@prameshj, as of this comment: #967 (comment), do i understand you correctly that you want to postpone work on this KEP until the next release cycle?

[prameshj]

@prameshj, as of this comment: #967 (comment), do i understand you correctly that you want to postpone work on this KEP until the next release cycle?

I will be working on it during this release cycle. I am just not sure it will get merged before October 6 since we have not gotten a ton of feedback from the community on this.

[mikejoh]

@prameshj I understand, if you at any time feel that you wont make it into 1.20 just let us know!

[prameshj]

This is going to target 1.21 milestone for alpha.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

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/test-infra repository.

[thockin]

This has not been a problem for most people since DNS caches on nodes became popular. Marking it as "old age", but it could be revived if a new owner appears.