Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

When scaling down pod replicas in ReplicaSets, it is supported to prioritize removing specified pods. #129396

Open
yangyefei90 opened this issue Dec 25, 2024 · 3 comments
Open

When scaling down pod replicas in ReplicaSets, it is supported to prioritize removing specified pods. #129396

yangyefei90 opened this issue Dec 25, 2024 · 3 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@yangyefei90
Copy link

What would you like to be added?

When scaling down pod replicas in ReplicaSets, it is supported to prioritize removing specified pods.

Why is this needed?

In actual production scenarios, we often encounter situations where users deploy applications using ReplicaSets and expect to prioritize the removal of specific pods during scaling down. I believe this is a reasonable requirement, as it provides convenience for users when working with ReplicaSets.
@yangyefei90 yangyefei90 added the kind/feature Categorizes issue or PR as related to a new feature. label Dec 25, 2024
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Dec 25, 2024
@k8s-ci-robot
Copy link
Contributor

There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:

  • /sig <group-name>
  • /wg <group-name>
  • /committee <group-name>

Please see the group list for a listing of the SIGs, working groups, and committees available.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Dec 25, 2024
@yangyefei90 yangyefei90 mentioned this issue Dec 25, 2024
Open
@googs1025
Copy link
Contributor

In stateless workloads such as deployment or ReplicaSets, we don't seem to need to focus on specific pods. 🤔

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@k8s-ci-robot @googs1025 @yangyefei90