-
Notifications
You must be signed in to change notification settings - Fork 111
Fix Volcano instaillation guide/ Add gang scheduling configuration in /config dir / Add unit test
#611
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
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for kubernetes-sigs-lws ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: JesseStutler The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Hi @JesseStutler. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
|
/cc @kerthcet @ardaguclu |
|
Gang-scheduling is an important feature. It would be better if you could update the examples in |
@LuyuZhang00 Yes I will also add content to site in later PRs, otherwise this PR may contain too many seperate contents |
|
/ok-to-test |
config/rbac/role.yaml
Outdated
| - get | ||
| - patch | ||
| - update | ||
| # If you want to enable gang scheduling with volcano, you need to uncomment the following section |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In my opinion, this role can be located under its dedicated file in https://github.com/kubernetes-sigs/lws/tree/main/config/rbac. User just needs to enable it in here https://github.com/kubernetes-sigs/lws/blob/main/config/rbac/kustomization.yaml (by default it can be commented out). This would align more kustomize way.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, thanks for your suggestion. I have modified now, please check
2. Add gang scheduling configuration in /config dir 3. Add unit test for CalculatePGMinResources Signed-off-by: JesseStutler <[email protected]>
|
/assign |
| apiVersion: rbac.authorization.k8s.io/v1 | ||
| kind: ClusterRole | ||
| metadata: | ||
| name: lws-volcano-role |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we can avoid creating a new ClusterRole lws-volcano-role here and instead reuse an existing ClusterRole, it would be more consistent with Helm.
Then we can use the patches mechanism in config/default/kustomization.yaml.
Would this be better?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#611 (comment), at first I add the volcano related cluster role in the config/rbac/role.yaml but @ardaguclu suggested that I can seperate a lws-volcano-role so I followed it. So what should I do now 😂
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we update role.yaml, in any case this role will be added. But this functionality is optional. So that in my opinion it is better to have it separately.
What type of PR is this?
/kind documentation
/kind feature
What this PR does / why we need it
Which issue(s) this PR fixes
NONE
Special notes for your reviewer
Does this PR introduce a user-facing change?