-
Notifications
You must be signed in to change notification settings - Fork 276
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
TAS: Introduce API #3235
TAS: Introduce API #3235
Conversation
✅ Deploy Preview for kubernetes-sigs-kueue canceled.
|
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.
It seems that the Workload API is quite different from the KEP, right?
https://github.com/kubernetes-sigs/kueue/tree/main/keps/2724-topology-aware-schedling#internal-apis
Yes, it is changed a bit, I will send the Workload API level in a separate PR, and will send a PR to update the KEP. |
I would like to merge this PR after we check how this Workload API changes give to the TAS scheduler in the updated KEP. |
4f190aa
to
8979606
Compare
Makes sense, I prepared the update: #3237 |
24dc823
to
a9111f8
Compare
FYI, the content here is in-sync with the KEP update PR (after the sync today). |
nit: Could we start comments with lowercase letters? |
I use lowercase for fields which follows https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status. It makes sense so tat in the generated user-facing docs it looks consistent with the json fields. As for labels and annotations I don't think there is such a convention. We also don't generate docs based on the declarations. Finally all consts here are commented with upper-case. |
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.
Thank you!
/lgtm
/approve
LGTM label has been added. Git tree hash: cd5fe89295a9751d5580fc9733fea98140fa9755
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mimowo, tenzen-y The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
As the API update in KEP is merged |
/release-note-edit
|
What type of PR is this?
/kind feature
What this PR does / why we need it:
Which issue(s) this PR fixes:
Part of #2724
Special notes for your reviewer:
Some of the field API comments are improved compared to KEP. I will update the KEP accordingly to make them in-sync.
Does this PR introduce a user-facing change?