Skip to content

Expanded DNS configuration #2595

Closed
Closed

Description

@gjkim42

Enhancement Description

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

Activity

  1. added
    needs-sigIndicates an issue or PR lacks a `sig/foo` label and requires one.
    on Apr 2, 2021
  2. gjkim42 commented on Apr 6, 2021

    @gjkim42
    MemberAuthor

    /sig network

  3. added
    sig/networkCategorizes an issue or PR as relevant to SIG Network.
    and removed
    needs-sigIndicates an issue or PR lacks a `sig/foo` label and requires one.
    on Apr 6, 2021
  4. JamesLaverack commented on May 1, 2021

    @JamesLaverack
    Member

    /milestone v1.22
    /stage alpha

  5. added
    stage/alphaDenotes an issue tracking an enhancement targeted for Alpha status
    on May 1, 2021
  6. added this to the v1.22 milestone on May 1, 2021
  7. added
    tracked/yesDenotes an enhancement issue is actively being tracked by the Release Team
    on May 1, 2021
  8. gracenng commented on May 10, 2021

    @gracenng
    Member

    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!

  9. gracenng commented on May 11, 2021

    @gracenng
    Member

    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!

  10. gjkim42 commented on May 11, 2021

    @gjkim42
    MemberAuthor

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

  11. gracenng commented on Jun 23, 2021

    @gracenng
    Member

    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

  12. gjkim42 commented on Jun 23, 2021

    @gjkim42
    MemberAuthor

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

  13. added
    tracked/noDenotes an enhancement issue is NOT actively being tracked by the Release Team
    and removed
    tracked/yesDenotes an enhancement issue is actively being tracked by the Release Team
    on Aug 19, 2021
  14. 83 remaining items

  15. modified the milestones: v1.28, v1.30 on Aug 17, 2023
  16. npolshakova commented on Sep 7, 2023

    @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?)

  17. gjkim42 commented on Sep 7, 2023

    @gjkim42
    MemberAuthor

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

  18. npolshakova commented on Sep 7, 2023

    @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

  19. removed
    lead-opted-inDenotes that an issue has been opted in to a release
    on Sep 7, 2023
  20. moved this from GA to Done in SIG Network KEPson Jan 18, 2024
  21. k8s-triage-robot commented on Jan 27, 2024

    @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

  22. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Jan 27, 2024
  23. salehsedghpour commented on Feb 9, 2024

    @salehsedghpour

    /milestone clear

  24. removed this from the v1.30 milestone on Feb 9, 2024
  25. moved this from GA to Done in KEPs I am trackingon May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.sig/networkCategorizes an issue or PR as relevant to SIG Network.stage/stableDenotes an issue tracking an enhancement targeted for Stable/GA status

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions