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

Respect PodTopologySpread after rolling upgrades #3243

Open
2 of 4 tasks
denkensk opened this issue Mar 18, 2022 · 8 comments
Open
2 of 4 tasks

Respect PodTopologySpread after rolling upgrades #3243

denkensk opened this issue Mar 18, 2022 · 8 comments
Assignees
Labels
sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team
Milestone

Comments

@denkensk
Copy link
Member

denkensk commented Mar 18, 2022

Enhancement Description

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

@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Mar 18, 2022
@denkensk
Copy link
Member Author

denkensk commented Mar 18, 2022

/sig scheduling

@k8s-ci-robot k8s-ci-robot added sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Mar 18, 2022
@denkensk
Copy link
Member Author

denkensk commented Jun 9, 2022

/assign

@ahg-g
Copy link
Member

ahg-g commented Jun 15, 2022

/milestone v1.25

@k8s-ci-robot k8s-ci-robot added this to the v1.25 milestone Jun 15, 2022
@Priyankasaggu11929 Priyankasaggu11929 added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Jun 15, 2022
@Priyankasaggu11929
Copy link
Member

Priyankasaggu11929 commented Jun 15, 2022

Hello @denkensk 👋, 1.25 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PST on Thursday June 23, 2022.

For note, This enhancement is targeting for stage alpha for 1.25 (correct me, if otherwise)

Here's where this enhancement currently stands:

  • KEP file using the latest template has been merged into the k/enhancements repo.
  • KEP status is marked as implementable
  • KEP has a updated detailed 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.

For note, 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
Copy link

Atharva-Shinde commented Jul 25, 2022

Hi @denkensk Enhancements team here again 👋

Checking in as we approach Code Freeze at 01:00 UTC on Wednesday, 3rd August 2022.

Please ensure that the following items are completed before the code-freeze:

  • All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
  • All PRs are fully merged by the code freeze deadline.

Currently, the status of the enhancement is marked as at-risk

Thanks :)

@Atharva-Shinde
Copy link

Atharva-Shinde commented Aug 1, 2022

Hey @denkensk as kubernetes/kubernetes#111441 PR is now merged and included in the issue description, I have marked this enhancement as tracked :)

@ahg-g
Copy link
Member

ahg-g commented Aug 5, 2022

@denkensk can you please open a docs PR?

@denkensk
Copy link
Member Author

denkensk commented Aug 6, 2022

Sorry. I created it before, forgot to link it with this issue. kubernetes/website#35165

@rhockenbury rhockenbury added tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team and removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels Sep 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team
Projects
None yet
Development

No branches or pull requests

6 participants