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

[Summer OSPP 2024] Karmada evenly allocates the replicas based on the spread constraint #5159

Closed
3 tasks done
whitewindmills opened this issue Jul 9, 2024 · 7 comments
Closed
3 tasks done
Assignees

Comments

@whitewindmills
Copy link
Member

whitewindmills commented Jul 9, 2024

Overview

Karmada (Kubernetes Armada) is a Kubernetes management system that enables you to run cloud-native applications in multiple Kubernetes clusters and cloud platforms without changing the application. By using Kubernetes native APIs and providing advanced scheduling capabilities, Karmada implements truly open, multi-cloud Kubernetes.

In Karmada's current scheduler replica allocation strategy, we already support four replica allocation methods: Duplicated, Aggregated, Static Weight, and Dynamic Weight. However, for more complex scheduling scenarios: after cross-AZ distribution constraints, the number of replicas of the workload is propagated as evenly as possible in the selected cluster. Currently, Karmada cannot support such scenarios well.

Therefore, we plan to semantically sort out the current Karmada scheduling strategy, determine whether to expand the existing API or change the original API design, and finally introduce this feature to meet the scheduling needs of more scenarios.

Project link

https://summer-ospp.ac.cn/org/prodetail/245c40281?lang=zh&list=pro

Reference issue

#4805

Tasks

@whitewindmills
Copy link
Member Author

/assign @ipsum-0320

@karmada-bot
Copy link
Collaborator

@whitewindmills: GitHub didn't allow me to assign the following users: ipsum-0320.

Note that only karmada-io members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @ipsum-0320

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.

@whitewindmills
Copy link
Member Author

@ipsum-0320 pls assign to yourself.

@ipsum-0320
Copy link
Contributor

/assign

@ipsum-0320
Copy link
Contributor

@whitewindmills All PRs have been merged. Thank you for your guidance; I have gained a lot from this open-source activity.

@RainbowMango
Copy link
Member

Thanks both of you @ipsum-0320 @whitewindmills for the hard work!

I'm going to close this as all tasks done.
/close

@karmada-bot
Copy link
Collaborator

@RainbowMango: Closing this issue.

In response to this:

Thanks both of you @ipsum-0320 @whitewindmills for the hard work!

I'm going to close this as all tasks done.
/close

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.

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

No branches or pull requests

4 participants