Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expanded DNS configuration #2595

Open
8 tasks done
gjkim42 opened this issue Apr 2, 2021 · 28 comments
Open
8 tasks done

Expanded DNS configuration #2595

gjkim42 opened this issue Apr 2, 2021 · 28 comments
Assignees
Labels
lead-opted-in Denotes that an issue has been opted in to a release sig/network Categorizes an issue or PR as relevant to SIG Network. stage/beta Denotes an issue tracking an enhancement targeted for Beta status tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team
Milestone

Comments

@gjkim42
Copy link
Member

gjkim42 commented Apr 2, 2021

Enhancement Description

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

@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Apr 2, 2021
@gjkim42
Copy link
Member Author

gjkim42 commented Apr 6, 2021

/sig network

@k8s-ci-robot k8s-ci-robot added sig/network Categorizes an issue or PR as relevant to SIG Network. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Apr 6, 2021
@aojea aojea added this to New KEPs in SIG-Network KEPs Apr 17, 2021
@JamesLaverack
Copy link
Member

JamesLaverack commented May 1, 2021

/milestone v1.22
/stage alpha

@k8s-ci-robot k8s-ci-robot added the stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status label May 1, 2021
@k8s-ci-robot k8s-ci-robot added this to the v1.22 milestone May 1, 2021
@JamesLaverack JamesLaverack added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label May 1, 2021
@gracenng
Copy link
Member

gracenng commented May 10, 2021

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
Copy link
Member

gracenng commented May 11, 2021

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
Copy link
Member Author

gjkim42 commented May 11, 2021

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
Copy link
Member

gracenng commented Jun 23, 2021

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
Copy link
Member Author

gjkim42 commented Jun 23, 2021

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 :)

@salaxander salaxander added tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team and removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels Aug 19, 2021
@thockin
Copy link
Member

thockin commented Sep 3, 2021

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

@gjkim42
Copy link
Member Author

gjkim42 commented Sep 3, 2021

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

Will discuss about the beta promotion later.

@k8s-triage-robot
Copy link

k8s-triage-robot commented Dec 2, 2021

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 2, 2021
@gjkim42
Copy link
Member Author

gjkim42 commented Dec 2, 2021

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 2, 2021
@thockin
Copy link
Member

thockin commented Feb 16, 2022

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

@k8s-triage-robot
Copy link

k8s-triage-robot commented May 17, 2022

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 17, 2022
@gjkim42
Copy link
Member Author

gjkim42 commented May 18, 2022

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 18, 2022
@thockin thockin modified the milestones: v1.25, v1.26 Jul 7, 2022
@bowei
Copy link
Member

bowei commented Aug 16, 2022

@gjkim42 -- is there a list of container runtimes that we need to check up on to see whether or not this can move forward?

Can we add this to the KEP?

@aojea
Copy link
Member

aojea commented Aug 16, 2022

@gjkim42 -- is there a list of container runtimes that we need to check up on to see whether or not this can move forward?

Can we add this to the KEP?

@bowei #2884

@thockin
Copy link
Member

thockin commented Sep 29, 2022

@gjkim42 Are we trying to push this to Beta for 1.26?

@thockin thockin added the lead-opted-in Denotes that an issue has been opted in to a release label Sep 29, 2022
@rhockenbury
Copy link

rhockenbury commented Sep 30, 2022

I'm going to remove the lead-opted-in label for now. Feel free to add it again if you decide to opt in for v1.26.

/remove-label lead-opted-in

@k8s-ci-robot k8s-ci-robot removed the lead-opted-in Denotes that an issue has been opted in to a release label Sep 30, 2022
@gjkim42
Copy link
Member Author

gjkim42 commented Oct 3, 2022

Are we trying to push this to Beta for 1.26?

Yes, I'd like to promote this feature to beta in 1.26.

@rhockenbury
Copy link

rhockenbury commented Oct 3, 2022

Okay, keep in mind enhancement freeze is this upcoming Thursday.

/label lead-opted-in
/milestone v1.26
/label tracked/yes
/remove-label tracked/no
/stage beta

@k8s-ci-robot k8s-ci-robot added lead-opted-in Denotes that an issue has been opted in to a release stage/beta Denotes an issue tracking an enhancement targeted for Beta status tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team and removed stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team labels Oct 3, 2022
@thockin
Copy link
Member

thockin commented Oct 3, 2022

All we need by deadline is any edits to the KEP itself, right?

@rhockenbury
Copy link

rhockenbury commented Oct 3, 2022

Right, edits to the kep yaml, kep readme and PRR review file. The requirements for enhancements freeze are:

  • KEP readme using the latest template has been merged into the k/enhancements repo.
  • KEP status is marked as implementable for latest-milestone: 1.26
  • KEP readme has a updated detailed test plan section filled out
  • KEP readme has up to date graduation criteria
  • KEP has a production readiness review that has been completed and merged into k/enhancements.

@aojea
Copy link
Member

aojea commented Oct 6, 2022

Right, edits to the kep yaml, kep readme and PRR review file. The requirements for enhancements freeze are:

  • KEP readme using the latest template has been merged into the k/enhancements repo.
  • KEP status is marked as implementable for latest-milestone: 1.26
  • KEP readme has a updated detailed test plan section filled out
  • KEP readme has up to date graduation criteria
  • KEP has a production readiness review that has been completed and merged into k/enhancements.

@gjkim42 you have to address those issues ^ on the KEP before you can promote the feature

@gjkim42
Copy link
Member Author

gjkim42 commented Oct 6, 2022

I think they are all done by #2884.

@rhockenbury
Copy link

rhockenbury commented Oct 6, 2022

With #2884 merged, I have this marked as tracked for v1.26

@aojea
Copy link
Member

aojea commented Oct 7, 2022

👏

@thockin thockin moved this from Alpha gated (code is merged) to Beta gated (merged) in SIG-Network KEPs Oct 14, 2022
@ruheenaansari34
Copy link

ruheenaansari34 commented Nov 2, 2022

Hi @gjkim42 👋,

Checking in once more as we approach the 1.26 code freeze at 17:00 PDT on Tuesday 8th November 2022.

Please ensure the following items are completed:

  • 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 fully merged by the code freeze deadline.

Let me know if we need to track any PRs beyond kubernetes/kubernetes#112824. If you do have any other k/k PRs open, please link them to this issue.

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

@gjkim42
Copy link
Member Author

gjkim42 commented Nov 2, 2022

All PRs related to this feature have been merged.

Thanks, @ruheenaansari34.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lead-opted-in Denotes that an issue has been opted in to a release sig/network Categorizes an issue or PR as relevant to SIG Network. stage/beta Denotes an issue tracking an enhancement targeted for Beta status tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team
Projects
Status: Graduating
SIG-Network KEPs
Beta gated (merged)
Development

No branches or pull requests