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
    • Remove PodHostIPs feature gates kubernetes#128634
  • 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

[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

[thockin]

Who will send the cleanup PR?

[SergeyKanzhelev]

mentioned by @pacoxu one comment above: kubernetes/kubernetes#126752

[haircommander]

/milestone v1.32

[impact-maker]

Hello @haircommander @wzshiming 👋, v1.32 Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 11th October 2024 / 19:00 PDT Thursday 10th October 2024.

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

Here's where this enhancement currently stands:

• KEP readme using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: v1.32.
• KEP readme has up-to-date graduation criteria.
• KEP has submitted a production readiness review request for approval and has a reviewer assigned.
• KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here). If your production readiness review is not completed yet, please make sure to fill the production readiness questionnaire in your KEP by the PRR Freeze deadline on Thursday 3rd October 2024 so that the PRR team has enough time to review your KEP.

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

• KEP status is marked as implementable for latest-milestone: v1.32.

[thockin]

@impact-maker This KEP is GA and ready to be completed. Can you clarify what we are looking for with "KEP status is marked as implementable for latest-milestone: v1.32" ?

[tjons]

Hi @thockin - enhancements lead here. @impact-maker is referring to the kep.yaml file - to be considered for enhancements freeze, https://github.com/kubernetes/enhancements/blob/master/keps/sig-network/2681-pod-host-ip/kep.yaml#L8 must specify that it is targeting the 1.32 release. Once that's done, this enhancement will be tracked for v1.32!

[kannon92]

I don't know if that is really necessary here. I think the only work needed is to drop the feature gate. I really don't see a need to track this in that way.

[danwinship]

Yeah, this doesn't really need to be tracked, and we probably don't want to update the latest-milestone, though probably we should make a point of going back through old KEPs and making sure the kep.yamls are all correct. (Clearly this should have been updated from implementable to implemented at some point...)

[aojea]

It seems the work remaining is to remove teh code completely

	PodHostIPs: {
		{Version: version.MustParse("1.28"), Default: false, PreRelease: featuregate.Alpha},
		{Version: version.MustParse("1.29"), Default: true, PreRelease: featuregate.Beta},
		{Version: version.MustParse("1.30"), Default: true, PreRelease: featuregate.GA, LockToDefault: true}, // remove in 1.32
	},

any volunteers to remove the code and just close this?

[thockin]

Right. This is, for all practical purposes, done.

…

On Mon, Oct 7, 2024 at 6:07 AM Antonio Ojea ***@***.***> wrote: It seems the work remaining is to remove teh code completely PodHostIPs: { {Version: version.MustParse("1.28"), Default: false, PreRelease: featuregate.Alpha}, {Version: version.MustParse("1.29"), Default: true, PreRelease: featuregate.Beta}, {Version: version.MustParse("1.30"), Default: true, PreRelease: featuregate.GA, LockToDefault: true}, // remove in 1.32 }, — Reply to this email directly, view it on GitHub <#2681 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABKWAVBY6ENSLGHFQWTLGITZ2KBSDAVCNFSM44GD2EVKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMZZGY4DQMRUGE3A> . You are receiving this because you were mentioned.Message ID: <kubernetes/enhancements/issues/2681/2396882416 ***@***.*** com>

[kannon92]

@aojea This is already up: kubernetes/kubernetes#126752

[tjons]

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

If you would be so kind, can you be sure to update the kep.yaml status to implemented so future enhancements teams do not have questions around this? Thanks!

[hacktivist123]

Hello @thockin 👋 1.32 Docs Shadow here.

Does this enhancement work planned for 1.32 require any new docs or modifications to existing docs?
If so, please follow the steps here to open a PR against the dev-1.32 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday, October 24th 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!

[rytswd]

Hi @thockin 👋 -- this is Ryota (@rytswd) from the v1.32 Communications Team!

For the v1.32 release, we are currently in the process of collecting and curating a list of potential feature blogs, and we'd love for you to consider writing one for your enhancement!

As you may be aware, feature blogs are a great way to communicate to users about features which fall into (but not limited to) the following categories:

• This introduces some breaking change(s)
• This has significant impacts and/or implications to users
• ...Or this is a long-awaited feature, which would go a long way to cover the journey more in detail 🎉

To opt in to write a feature blog, could you please let us know and open a "Feature Blog placeholder PR" (which can be only a skeleton at first) against the website repository by Wednesday, 30th Oct 2024? For more information about writing a blog, please find the blog contribution guidelines 📚

Tip

Some timeline to keep in mind:

• 02:00 UTC Wednesday, 30th Oct: Feature blog PR freeze
• Monday, 25th Nov: Feature blogs ready for review
• You can find more in the release document

Note

In your placeholder PR, use XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release.

[hacktivist123]

Hello, @thockin 👋 1.32 Docs Shadow here.

This is just a reminder to open a placeholder PR against dev-1.32 branch in the k/website repo for this (steps available here) for this KEP if it requires new or modifications to existing docs:

The deadline for this is Thursday, Oct 24 at 18:00 PDT.
Thanks! 🚀

[danwinship]

@hacktivist123 There is no docs update needed; this KEP was already completed in 1.30, and the only work that was done in 1.32 was to remove the old feature gate

[hacktivist123]

Thanks @danwinship

[rytswd]

Hi @thockin @danwinship 👋, v1.32 Communications Team here again!

From the nature of the change in v1.32 (thanks to @danwinship's clarification above), I'm assuming there will be no blog write-up planned for this change. But for the completeness of the Release tracking, please bear with me on one last reminder of the feature blog deadline mentioned above, which is 02:00 UTC Wednesday, 30th Oct. 🙏

I'll leave the same information just in case this catches anyone's eyes:

Tip

Some timeline to keep in mind:

• 02:00 UTC Wednesday, 30th Oct: Feature blog PR freeze
• Monday, 25th Nov: Feature blogs ready for review
• You can find more in the release document

Note

In your placeholder PR, use XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release.

[thockin]

Once 32 goes out, we can close this. Yay!

kep.yaml still indicates "implementable", though

[tjons]

Hey again @haircommander @thockin 👋 v1.32 Enhancements team here,

Just checking in as we approach code freeze at 02:00 UTC Friday 8th November 2024 / 19:00 PDT Thursday 7th November 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):

• Remove PodHostIPs feature gates in 1.32 kubernetes#126752

Additionally, please let me know if there are any other PRs in k/k not listed in the description or not linked with this GitHub issue that we should track for this KEP, so that we can maintain accurate status.

The status of this enhancement is marked as at risk for code freeze.

If you anticipate missing code freeze, you can file an exception request in advance. Thank you!

[thockin]

PR kubernetes/kubernetes#128634 replaces kubernetes/kubernetes#126752

[thockin]

Gate has been removed. Hooray