search

kubernetes / enhancements

Enhancements tracking repo for Kubernetes
Apache License 2.0
3.4k stars 1.47k forks source link

Field `status.hostIPs` added for Pod #2681

Open wzshiming opened 3 years ago

wzshiming commented 3 years ago

Enhancement Description

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

wzshiming commented 3 years ago

/sig node /sig network

k8s-triage-robot commented 3 years ago

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:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 3 years ago

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:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

wzshiming commented 2 years ago

/remove-lifecycle rotten

hosseinsalahi commented 2 years ago

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:

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 commented 2 years ago

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 commented 2 years ago

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

k8s-triage-robot commented 2 years ago

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:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

wzshiming commented 2 years ago

/remove-lifecycle stale

thockin commented 2 years ago

I have not heard anything on this. The PR is full of conflicts - @wzshiming do you want to try to get code into 1.26?

wzshiming commented 2 years ago

I have not heard anything on this. The PR is full of conflicts - @wzshiming do you want to try to get code into 1.26?

Yes, I rebased the PR, please take a look at it when you have time. Thank you. #109616

marosset commented 2 years ago

/milestone v1.26 /label lead-opted-in (I'm doing this on behalf of @ruiwen-zhao / SIG-node)

rhockenbury commented 2 years ago

Hello @wzshiming @thockin 👋, 1.26 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PDT on Thursday 6th October 2022.

This enhancement is targeting for stage alpha for 1.26 (correct me, if otherwise)

Here's where this enhancement currently stands:

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

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

rhockenbury commented 2 years ago

/stage alpha /label tracked/yes

derekwaynecarr commented 2 years ago

/label lead-opt-in

sig-network is primary owner.

k8s-ci-robot commented 2 years ago

@derekwaynecarr: The label(s) `/label lead-opt-in

cannot be applied. These labels are supported:api-review, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, team/katacoda, refactor, lead-opted-in, tracked/no, tracked/out-of-tree, tracked/yes`

In response to [this](https://github.com/kubernetes/enhancements/issues/2681#issuecomment-1265973364): >/label lead-opt-in > >sig-network is primary owner. Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
aojea commented 1 year ago

Hello @wzshiming @thockin 👋, 1.26 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PDT on Thursday 6th October 2022.

This enhancement is targeting for stage alpha for 1.26 (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: 1.26
  • [ ] KEP readme has a updated detailed test plan section filled out
  • [x] KEP readme has up to date graduation criteria
  • [x] KEP has a production readiness review that has been completed and merged into k/enhancements.

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

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

@wzshiming you have to fix the 3 missing points in the KEP mentioned in https://github.com/kubernetes/enhancements/issues/2681#issuecomment-1264188068

rhockenbury commented 1 year ago

Hello 👋, 1.26 Enhancements Lead here.

Unfortunately, this enhancement did not meet requirements for enhancements freeze.

If you still wish to progress this enhancement in v1.26, please file an exception request. Thanks!

/milestone clear /label tracked/no /remove-label tracked/yes /remove-label lead-opted-in

Rishit-dagli commented 1 year ago

Is this KEP still being tracked for 1.26 if so,

This enhancement is marked as ‘Needs Docs’ for 1.26 release. Please follow the steps detailed in the documentation to open a PR against dev-1.26 branch in the k/website repo. This PR can be just a placeholder at this time, and must be created by November 9. Also, take a look at Documenting for a release to familiarize yourself with the docs requirement for the release.

Thank you!

SergeyKanzhelev commented 1 year ago

/label lead-opt-in

sig network is still the primary owners though

k8s-ci-robot commented 1 year ago

@SergeyKanzhelev: The label(s) `/label lead-opt-in

cannot be applied. These labels are supported:api-review, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, team/katacoda, refactor, lead-opted-in, tracked/no, tracked/out-of-tree, tracked/yes. Is this label configured underlabels -> additional_labelsorlabels -> restricted_labelsinplugin.yaml`?

In response to [this](https://github.com/kubernetes/enhancements/issues/2681#issuecomment-1414183626): >/label lead-opt-in > >sig network is still the primary owners though Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
SergeyKanzhelev commented 1 year ago

/label lead-opted-in

Atharva-Shinde commented 1 year ago

Hello @wzshiming @thockin 👋, Enhancements team here.

Just checking in as we approach Enhancements freeze on 18:00 PDT Thursday 9th February 2023.

This enhancement is targeting for stage alpha for 1.27 (correct me, if otherwise)

Here's where this enhancement currently stands:

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

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

wzshiming commented 1 year ago

I created the update, please take a look at #3848

Atharva-Shinde commented 1 year ago

I created the update, please take a look at https://github.com/kubernetes/enhancements/pull/3848

@wzshiming looks like the PR addresses all the changes needed, please do get it reviewed and merged before the Enhancements Freeze :)

Atharva-Shinde commented 1 year ago

@wzshiming, With all the KEP requirements in place and merged into k/enhancements, this enhancement is all good for the upcoming enhancements freeze. 🚀

The status of this enhancement is marked as tracked. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

Atharva-Shinde commented 1 year ago

Hey again @wzshiming 👋 Enhancements team here, Just checking in as we approach 1.27 code freeze at 17:00 PDT on Tuesday 14th March 2023.

Here's where this enhancement currently stands:

For this enhancement, it looks like the following PR/s are open and need to be merged before code freeze:

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!

marosset commented 1 year ago

Unfortunately the implementation PRs associated with this enhancement have not merged by code-freeze so this enhancement is getting removed from the release.

If you would like to file an exception please see https://github.com/kubernetes/sig-release/blob/master/releases/EXCEPTIONS.md

/milestone clear /remove-label tracked/yes /label tracked/no

k8s-ci-robot commented 1 year ago

@marosset: Those labels are not set on the issue: tracked/yes

In response to [this](https://github.com/kubernetes/enhancements/issues/2681#issuecomment-1469050641): >Unfortunately the implementation PRs associated with this enhancement have not merged by code-freeze so this enhancement is getting removed from the release. > >If you would like to file an exception please see https://github.com/kubernetes/sig-release/blob/master/releases/EXCEPTIONS.md > >/milestone clear >/remove-label tracked/yes >/label tracked/no > Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
SergeyKanzhelev commented 1 year ago

@wzshiming do you plan to work on this in 1.28?

wzshiming commented 1 year ago

Yeah, I will continue to work on this

SergeyKanzhelev commented 1 year ago

Can you pls send the PR to update the target milestone.

/milestone v1.28

wzshiming commented 1 year ago

I've sent the PR #4038

ruheenaansari34 commented 1 year ago

Hello @wzshiming 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on 1:00 UTC on Friday 16th June 2023.

This enhancement is targeting stage alpha for 1.28 (correct me, if otherwise)

Here’s where this enhancement currently stands:

With all the KEP requirements in place and merged into k/enhancements, this enhancement is all good for the upcoming enhancements freeze. 🚀

The status of this enhancement is marked as tracked. Please keep the issue description up-to-date with the appropriate stages as well. Thank you!

VibhorChinda commented 1 year ago

Hello @wzshiming @thockin :wave:, 1.28 Docs Shadow here.

Does this enhancement work planned for 1.28 require any new docs or modification to existing docs?

If so, please follows the steps here to open a PR against dev-1.28 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday 20th July 2023.

Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.

Thank you!

Rishit-dagli commented 1 year ago

Hey @wzshiming , could you please create a docs PR even if it is a draft PR with no content yet against dev-1.28 branch in the k/website repo. The deadline to create this draft PR is Thursday 20th July 2023.

wzshiming commented 1 year ago

thanks @Rishit-dagli, @VibhorChinda

done https://github.com/kubernetes/website/pull/42003

ruheenaansari34 commented 1 year ago

Hey again @wzshiming 👋

Just checking in as we approach Code freeze at 01:00 UTC Friday, 19th July 2023.

Here’s the enhancement’s state for the upcoming code freeze:

These are the code related PR/s that I found on this KEP issue

Please keep the issue description up-to-date with all the PR/s that are associated with this KEP and let me know if there are other PR/s in k/k we should be tracking for this KEP.

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

Atharva-Shinde commented 1 year ago

Hey @ruheenaansari34 👋 Enhancements Lead here, With https://github.com/kubernetes/kubernetes/pull/109616 merged as per the issue description, this enhancement is now tracked for v1.28 Code Freeze. Thanks!

VibhorChinda commented 1 year ago

Hello @wzshiming :wave: please take a look at Documenting for a release - PR Ready for Review to get your PR ready for review before Tuesday 25th July 2023. Thank you!

thockin commented 1 year ago

I am tracking this for beta in 1.29 - is that correct?

wzshiming commented 1 year ago

Yep, thanks.

SergeyKanzhelev commented 1 year ago

/stage beta

npolshakova commented 1 year ago

Hi @wzshiming 👋, 1.29 Enhancements team here!

Just checking in as we approach enhancements freeze on 01:00 UTC, Friday, 6th October, 2023.

This enhancement is targeting for stage beta for 1.29 (correct me, if otherwise)

Here's where this enhancement currently stands:

The status of this enhancement is marked as tracked for enhancement freeze 🚀.

harshitasao commented 11 months ago

Hi @wzshiming 👋, v1.29 Docs Shadow here Does this enhancement work planned for v1.29 require any new docs or modification to existing docs? If so, please follows the steps here to open a PR against dev-1.29 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday, 19 October 2023. Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release. Thank you!

a-mccarthy commented 11 months ago

hi @wzshiming 👋 from the v1.29 Release Team-Communications! We would like to check if you have any plans to publish a blog for this KEP regarding new features, removals, and deprecations for this release.

If so, you need to open a PR placeholder in the website repository. The deadline will be on Tuesday 14th November 2023 (after the Docs deadline PR ready for review)

Here is the 1.29 calendar

npolshakova commented 11 months ago

Hey again @wzshiming 👋 Enhancements team here,

Just checking in as we approach code freeze at 01:00 UTC Wednesday 1st November 2023: .

Here's where this enhancement currently stands:

For this enhancement, it looks like the following PRs was merged before code freeze:

With the merged and linked in the issue description, this KEP is tracked for code freeze.

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!

salehsedghpour commented 9 months ago

/remove-label lead-opted-in

salehsedghpour commented 8 months ago

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 commented 8 months ago

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