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

[feature request] WorkloadSpread should consider the update strategy where Pod is created before deletion. #834

Closed
veophi opened this issue Dec 6, 2021 · 0 comments
Assignees
Labels

Comments

@veophi
Copy link
Member

veophi commented Dec 6, 2021

What would you like to be added:
When the new Pod is created in this strategy, WorkloadSpread don't know which pod will be replaced, so cannot assign the new pod to the right subset.

  • WorkloadSpread should support rollingUpdate type for Deployment;
  • WorkloadSpread should support MaxSurge for CloneSet & Deployment;

Why is this needed:
For the better support to CloneSet & Deployment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants