search

kubernetes / enhancements

Enhancements tracking repo for Kubernetes
Apache License 2.0
3.39k stars 1.45k forks source link

Random Pod selection on ReplicaSet downscaling #2185

Closed alculquicondor closed 1 month ago

alculquicondor commented 3 years ago

Enhancement Description

MinpengJin commented 5 months ago

Is there anything else that needs to be done for this feature?

k8s-triage-robot commented 4 months ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

You can:

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

/close not-planned

k8s-ci-robot commented 4 months ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes/enhancements/issues/2185#issuecomment-2065634511): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages 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: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ 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.
xuzhenglun commented 4 months ago

/reopen This is open for contributors

Is there anything else required before GA? Could you please clarify the clues, and I'm glad to follow with that. @alculquicondor

alculquicondor commented 4 months ago

/reopen

Nothing major, just to follow the process of graduation: update KEP, answer any new PRR questions, update code.

k8s-ci-robot commented 4 months ago

@alculquicondor: Reopened this issue.

In response to [this](https://github.com/kubernetes/enhancements/issues/2185#issuecomment-2066514108): >/reopen > >Nothing major, just to follow the process of graduation: update KEP, answer any new PRR questions, update code. 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.
xuzhenglun commented 4 months ago

so, Iet's do that.

/assign @MinpengJin

k8s-triage-robot commented 3 months ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

You can:

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

/close not-planned

k8s-ci-robot commented 3 months ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes/enhancements/issues/2185#issuecomment-2126089602): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages 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: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ 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-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
xuzhenglun commented 3 months ago

/reopen /remove-lifecycle rotten

@alculquicondor can we target this in v1.31 ? https://github.com/kubernetes/enhancements/pull/4649

alculquicondor commented 3 months ago

yes, I'll put it in my review queue.

alculquicondor commented 3 months ago

/reopen

Oh, sorry, I thought this was a PR. I'm not planning on graduating this to Stable in v1.31, but I'm willing to assist others, if someone wants to take it.

k8s-ci-robot commented 3 months ago

@alculquicondor: Reopened this issue.

In response to [this](https://github.com/kubernetes/enhancements/issues/2185#issuecomment-2146042763): >/reopen > >Oh, sorry, I thought this was a PR. I'm not planning on graduating this to Stable in v1.31, but I'm willing to assist others, if someone wants to take it. 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-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
xuzhenglun commented 3 months ago

@alculquicondor

Actually, there is a PR waiting for review. please check the following link when you are convenient: https://github.com/kubernetes/enhancements/pull/4649

alculquicondor commented 3 months ago

Oh, I missed it. I just updated the description.

soltysh commented 2 months ago

/milestone v1.31 /stage stable /label lead-opted-in

sreeram-venkitesh commented 2 months ago

Hello @alculquicondor @MinpengJin @xuzhenglun 👋, v1.31 Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 14th June 2024 / 19:00 PDT Thursday 13th June 2024.

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

Here's where this enhancement currently stands:

For this KEP, everything is taken care of in https://github.com/kubernetes/enhancements/pull/4649. Please make sure that it is merged in time before the enhancements freeze.

The status of this enhancement is marked as at risk for enhancement freeze. I can mark it as tracked as soon as the above PR is merged however! Please link the relevant PRs for beta in the issue description as well.

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

sreeram-venkitesh commented 2 months ago

With #4649 merged, we can mark this KEP as tracked for enhancements freeze! 🎉

a-mccarthy commented 2 months ago

Hi @damemi @MinpengJin,

👋 from the v1.31 Communications Team! We'd love for you to opt in to write a feature blog about your enhancement! Some reasons why you might want to write a blog for this feature include (but are not limited to) if this introduces breaking changes, is important to our users, or has been in progress for a long time and is graduating.

To opt in, let us know and open a Feature Blog placeholder PR against the website repository by 3rd July, 2024. For more information about writing a blog see the blog contribution guidelines.

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.

Princesso commented 2 months ago

Hello @damemi , @MinpengJin 👋, 1.31 Docs Lead here. Does this enhancement work planned for 1.31 require any new docs or modification to existing docs? If so, please follow the steps here to open a PR against dev-1.31 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday June 27, 2024 18:00 PDT. Also, take a look at Documenting for a release to get yourself familiarised with the docs requirement for the release. Thank you!

a-mccarthy commented 2 months ago

Hello @damemi, @MinpengJin, friendly reminder about the upcoming blog opt-in and placeholder deadline on July 3rd. Please open a blog placeholder PR if you are interested in contributing a blog.

sreeram-venkitesh commented 2 months ago

Hey again @alculquicondor @damemi @MinpengJin 👋 v1.31 Enhancements team here,

Just checking in as we approach code freeze at 02:00 UTC Wednesday 24th July 2024 / 19:00 PDT Tuesday 23rd July 2024 .

Here's where this enhancement currently stands:

List of associated PRs:

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

This KEP is marked as Tracked for code freeze. Thanks a lot for keeping the issue description up to date! 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!

alculquicondor commented 2 months ago

I just added the documentation update PR that was missing in the description. With that, we are all set.

k8s-triage-robot commented 1 month ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

You can:

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

/close not-planned

k8s-ci-robot commented 1 month ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes/enhancements/issues/2185#issuecomment-2274227737): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages 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: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ 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-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.