Skip to content
This repository has been archived by the owner on May 25, 2023. It is now read-only.

Q: Would having one kube-batchd per namespace work? #192

Closed
vicaya opened this issue Mar 26, 2018 · 3 comments
Closed

Q: Would having one kube-batchd per namespace work? #192

vicaya opened this issue Mar 26, 2018 · 3 comments

Comments

@vicaya
Copy link

vicaya commented Mar 26, 2018

Unlike kube-quotalloc, it looks like that kube-batchd should be able to work in its own namespace isolated from others?

@k82cn
Copy link
Contributor

k82cn commented Mar 27, 2018

nop, similar to multi-scheduler: one kube-batched and one kube-scheduler are enough for the cluster :) kube-batched will use different schedulerName from kube-scheduler.

@vicaya
Copy link
Author

vicaya commented Mar 28, 2018

I knew that one kube-batchd would work :) My question is that if I deploy kube-batchd (potentially different versions/mods) per namespace with different scheduler names, as long as permission is granted, it should still work, right?

@k82cn
Copy link
Contributor

k82cn commented Mar 28, 2018

yes. make sure different kube-arbitrator using different scheduler name; and pod uses right scheduler name :)

@k82cn k82cn closed this as completed Apr 26, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants