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

Job Forward for multi-cluster scenario #880

Closed
k82cn opened this issue Jun 24, 2020 · 3 comments
Closed

Job Forward for multi-cluster scenario #880

k82cn opened this issue Jun 24, 2020 · 3 comments
Assignees
@k82cn
Labels
area/scheduling kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone
v1.1

Comments

@k82cn
Copy link
Member

k82cn commented Jun 24, 2020

Is this a BUG REPORT or FEATURE REQUEST?:

/kind feature

Description:

Currently, we'd like to support multi-cluster scenarios for volcano to support more workload. Here's some draft ideas, will update design doc soon:

  1. Use kubernetes/cluster-register as API of cluster info, e.g. endpoint, auth
  2. Add a new JobForwardor controller to forward job (PodGroup + Pod + ... ) to target cluster, xref Improve controller manager for new controller. #879
  3. Add a new forward.go action to balance nodes and remote cluster
@volcano-sh-bot volcano-sh-bot added the kind/feature Categorizes issue or PR as related to a new feature. label Jun 24, 2020
@k82cn
Copy link
Member Author

k82cn commented Jun 24, 2020

/assign
/area scheduling
/priority important-soon

@volcano-sh-bot volcano-sh-bot added area/scheduling priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Jun 24, 2020
This was referenced Jun 24, 2020
Closed
Merged
@hzxuzhonghu hzxuzhonghu added this to the v1.1 milestone Jul 17, 2020
@stale
Copy link

stale bot commented Oct 15, 2020

Hello 👋 Looks like there was no activity on this issue for last 90 days.
Do you mind updating us on the status? Is this still reproducible or needed? If yes, just comment on this PR or push a commit. Thanks! 🤗
If there will be no activity for 60 days, this issue will be closed (we can always reopen an issue if we need!).

@stale stale bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 15, 2020
@stale
Copy link

stale bot commented Dec 14, 2020

Closing for now as there was no activity for last 60 days after marked as stale, let us know if you need this to be reopened! 🤗

@stale stale bot closed this as completed Dec 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@k82cn k82cn

Labels
area/scheduling kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Milestone
v1.1
Development

No branches or pull requests
3 participants
@hzxuzhonghu @k82cn @volcano-sh-bot