-
Notifications
You must be signed in to change notification settings - Fork 40
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
feat: add component config #609
base: main
Are you sure you want to change the base?
Conversation
Welcome @rainfd! |
Hi @rainfd. 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. |
✅ Deploy Preview for kubernetes-sigs-jobset ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
/ok-to-test |
Thanks for working on this @rainfd, I will review this soon |
kubeConfig.QPS = *cfg.ClientConnection.QPS | ||
kubeConfig.Burst = int(*cfg.ClientConnection.Burst) |
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 the user sets both the qps flag and the configFile flag, will the qps flag not take effect? Have we considered this situation?
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 wouldn't take effect. Only configFile and featuregate flag is support in kueue currently.
Considering supporting both configuration files and command-line arguments requires to add spf13/viper like dependencies.
I just want to keep it simple.
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.
Thanks for your reply. so, config is the first priority. Once configured, flag will not take effect.
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.
I add this comment to the description.
FYI I am OOO for the next week or so but can review when I get back. |
c2555ca
to
7797b24
Compare
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: rainfd 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 |
Namespace *string `json:"namespace,omitempty"` | ||
|
||
// ControllerManager returns the configurations for controllers | ||
ControllerManager `json:",inline"` |
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.
Any reason this field json tag is inline with no name, where as others are not?
Same question for other fields in the file. Is it just for making the structure of the json less nested?
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.
Your guess is right. The basic structure come from kueue, and I think it was clear, so I didn't change it
Looks good, I would prefer to include a larger change like this in 0.7 release, rather than as a last minute addition to 0.6, so unless there's any objections that's what we'll do |
/hold |
Signed-off-by: rainfd <rainfd@live.cn>
7797b24
to
ea1ac2e
Compare
Fix: #55
The basic configuration follows kueue.