Field status.hostIPs added for Pod

[wzshiming]

Enhancement Description

• One-line enhancement description (can be used as a release note): Field status.hostIPs added for Pod
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/2681-pod-host-ip
• Discussion Link:
• Primary contact (assignee):
• Responsible SIGs:
  • sig-node
  • sig-network
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.28
  • Beta release target (x.y): 1.29
  • Stable release target (x.y): 1.30
• Alpha
  • KEP (k/enhancements) update PR(s):
    • KEP-2681: Field status.hostIPs added for Pod #2661
    • KEP-2681: Target to alpha for 1.27 #3794
    • KEP-2681: Target to alpha for 1.28 #4038
  • Code (k/k) update PR(s):
    • Field status.hostIPs added for Pod kubernetes#109616
  • Docs (k/website) update PR(s):
    • KEP-2681: Docs update for Alpha PodHostIPs website#42153
• Beta
  • KEP (k/enhancements) update PR(s):
    • Move KEP 2681 to Beta #4168
  • Code (k/k) update PR(s):
    • Promote KEP-2681 to beta in 1.29 kubernetes#121477
  • Docs (k/website) update PR(s):
    • [KEP-2681] Docs update for Beta PodHostIPs website#43448
• Stable
  • KEP (k/enhancements) update PR(s):
    • Move KEP 2681 to GA #4418
  • Code (k/k) update PR(s):
    • Promote KEP-2681 to GA in 1.30 kubernetes#122870
  • Docs (k/website) update PR(s):
    • KEP-2681 PodHostIPs in downward API to stable website#45297

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

[wzshiming]

/sig node
/sig network

[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

[k8s-triage-robot]

The Kubernetes project currently lacks enough active 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 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 rotten

[wzshiming]

/remove-lifecycle rotten

[hosseinsalahi]

Hello @wzshiming

v1.24 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00pm PT on Thursday Feb 3rd, 2022. This enhancement is targeting beta for v1.24, is this correct?

Here’s where this enhancement currently stands:

• Updated KEP file using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for this release
• KEP has a test plan section filled out.
• KEP has up to date graduation criteria.
• KEP has a production readiness review that has been completed and merged into k/enhancements.

The status of this enhancement is marked as at risk. Please update the issue description up-to-date with appropriate stages as well.
Thanks!

[gracenng]

The Enhancements Freeze is now in effect and this enhancement is removed from the release. Missing PRR for beta stage
Please feel free to file an exception.

/milestone clear

[wojtek-t]

@gracenng - this isn't targetted for beta, this is targetted for Alpha (so the KEP seem to be ok).

[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

[wzshiming]

/remove-lifecycle stale

[salehsedghpour]

Hello 👋 1.30 Enhancements Lead here,

I'm closing milestone 1.29 now,
If you wish to progress this enhancement in v1.30, please follow the instructions here to opt in the enhancement and make sure the lead-opted-in label is set so it can get added to the tracking board and finally add /milestone v1.30. Thanks!

/milestone clear

[thockin]

Pinging this after sig-net - let's decide if this moves to GA in 1.30

[aojea]

Pinging this after sig-net - let's decide if this moves to GA in 1.30

+1 @wzshiming are you able to work on this?

[wzshiming]

Of course, I will work on this soon.

[mickeyboxell]

Hello @thockin 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on [02:00 UTC Friday 9th February 2024 / 18:00 PDT Thursday 8th February 2024](https://everytimezone.com/s/1ade3dca):.

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

Here's where this enhancement currently stands:

• KEP readme using the [latest template](https://github.com/kubernetes/enhancements/tree/master/keps/NNNN-kep-template) has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: 1.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](https://github.com/kubernetes/community/blob/master/sig-architecture/production-readiness.md#submitting-a-kep-for-production-readiness-approval)).

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

• It looks like everything is all queued up in the PR: Move KEP 2681 to GA #4418 and will be good to go as soon as it's merged.

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!

[mickeyboxell]

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

[chanieljdan]

Hi @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,

👋 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 @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 @thockin 👋, could you review the above before the placeholder deadline tonight? Thanks!

[danwinship]

filed kubernetes/website#45297 for docs update

[sftim]

Is there a k/k PR to promote the feature to stable?

[mickeyboxell]

Hey again @danwinship 👋 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.

For this enhancement, it looks like the following PRs are open and need to be merged before code freeze (and we need to update the Issue description to include all the related PRs of this KEP):

• Promote KEP-2681 to GA in 1.30 kubernetes#122870

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!

[mickeyboxell]

Hey again @danwinship 👋 Enhancements team here,

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

• Promote KEP-2681 to GA in 1.30 kubernetes#122870

This enhancement is now marked as tracked for code freeze for the v1.30 Code Freeze!

The last thing to do is to update the status field in the kep.yaml file to implemented when the code PRs are merged and the feature gates are removed.

[thockin]

GA'ed in 30, Cleanup in 32

[sreeram-venkitesh]

Hi! v1.31 Enhancements lead here 👋🏼

I'm assuming the status will be updated to implemented in v1.32 along with the cleanup, right? I'll remove the lead-opted-in label and remove this KEP from the v1.31 tracking board. Please let me know if this works.

/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

[SergeyKanzhelev]

/remove-lifecycle stale

[kannon92]

#2681 (comment)

Moving this to "Proposed for consideration". The goal for 1.32 is to clean up the feature gates so the ask is very small from sig-node side.

[pacoxu]

@kannon92 This seems to be a cleanup only. Should we track this?

For tracking, we have only alpha/beta or ga stage. This is already after GA stage.

I would like to close this enhancement issue or open a cleanup PR on k/k to close this issue.

• FG remove pr: Remove PodHostIPs feature gates in 1.32 kubernetes#126752
• e2e Do not serial for tests of Pod Host IPs. kubernetes#126810