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.

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

KEP-3243: respect pod topology spread after rolling upgrades #3244

Conversation

denkensk
Copy link
Member

@denkensk denkensk commented Mar 18, 2022

Signed-off-by: Alex Wang [email protected]

  • One-line PR description: adding new KEP

Discussion Link
kubernetes/kubernetes#98215
kubernetes/kubernetes#105661

  • Other comments:

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Mar 18, 2022
@k8s-ci-robot k8s-ci-robot requested a review from ahg-g March 18, 2022 09:04
@k8s-ci-robot k8s-ci-robot added the kind/kep Categorizes KEP tracking issues and PRs modifying the KEP directory label Mar 18, 2022
@k8s-ci-robot k8s-ci-robot added the sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. label Mar 18, 2022
@denkensk
Copy link
Member Author

/cc @ahg-g @Huang-Wei @alculquicondor

@alculquicondor
Copy link
Member

Thanks!
I will review after code freeze

@ahg-g
Copy link
Member

ahg-g commented Mar 18, 2022

Can you link the discussion issue please.

/assign

@denkensk
Copy link
Member Author

Can you link the discussion issue please.

Done. Added in the top.

@alculquicondor
Copy link
Member

/unassign
Since I already reviewed the doc, one KEP reviewer should be enough.

@denkensk denkensk force-pushed the respect-pod-topology-spread-after-rolling-upgrades branch from 3be0398 to cb1e11d Compare April 29, 2022 04:04
@denkensk
Copy link
Member Author

@ahg-g
Thanks for your review. Updated. Pls review it again.

@wojtek-t wojtek-t self-assigned this Apr 29, 2022
@denkensk
Copy link
Member Author

denkensk commented May 6, 2022

@ahg-g
Thanks a lot.
Updated.
Pls review it again.

@ahg-g
Copy link
Member

ahg-g commented May 6, 2022

/lgtm

@wojtek-t this should be ready for PRR

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label May 6, 2022
Copy link
Member

@wojtek-t wojtek-t left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From PRR perspective it seems ok - I added two comments for tests.

I would also encourage you to fill in the scalability section of PRR now, but I'm not going to block on it.

persisted Pod object, otherwise it is silently dropped; moreover, kube-scheduler
will ignore the field and continue to behave as before.

### Test Plan
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

- Feature gate enable/disable tests
- `MatchLabelKeys` in `TopologySpreadConstraint` works as expected
- Benchmark tests:
- Verify no significant performance degradation
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In existing benchmarks? Or new ones?

I'm assuming existing don't exercise the newly added feature - are we ok with it?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I plan to benchmark this using the exist cases in k8s.io/kubernetes/test/integration/scheduler_perf to verify if there's no significant performance degradation.

@denkensk denkensk force-pushed the respect-pod-topology-spread-after-rolling-upgrades branch from 85c24e3 to ceee6ae Compare June 7, 2022 12:11
@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jun 7, 2022
@denkensk denkensk force-pushed the respect-pod-topology-spread-after-rolling-upgrades branch from ceee6ae to 1b45339 Compare June 7, 2022 12:20
@denkensk denkensk requested a review from wojtek-t June 7, 2022 12:22
@wojtek-t
Copy link
Member

wojtek-t commented Jun 8, 2022

/lgtm
/approve PRR

Thanks!

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jun 8, 2022
@ahg-g
Copy link
Member

ahg-g commented Jun 8, 2022

/approve
/lgtm

@ahg-g
Copy link
Member

ahg-g commented Jun 8, 2022

/hold

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 8, 2022
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ahg-g, denkensk, wojtek-t

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 8, 2022
@ahg-g
Copy link
Member

ahg-g commented Jun 8, 2022

/label tide/merge-method-squash

@k8s-ci-robot k8s-ci-robot added the tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. label Jun 8, 2022
@ahg-g
Copy link
Member

ahg-g commented Jun 8, 2022

/hold cancel

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 8, 2022
@k8s-ci-robot k8s-ci-robot merged commit 957af70 into kubernetes:master Jun 8, 2022
@k8s-ci-robot k8s-ci-robot added this to the v1.25 milestone Jun 8, 2022
@denkensk denkensk deleted the respect-pod-topology-spread-after-rolling-upgrades branch June 9, 2022 03:16
pacoxu added a commit to DaoCloud-OpenSource/docs that referenced this pull request Aug 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/kep Categorizes KEP tracking issues and PRs modifying the KEP directory lgtm "Looks good to me", indicates that a PR is ready to be merged. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants