-
Notifications
You must be signed in to change notification settings - Fork 4k
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
implemented TemplateNodeInfo function #3671
implemented TemplateNodeInfo function #3671
Conversation
Welcome @wangshiqi308! |
/assign @ysy2020 @RainbowMango |
/lgtm |
/assign @RainbowMango |
cluster-autoscaler/cloudprovider/huaweicloud/huaweicloud_service_manager.go
Outdated
Show resolved
Hide resolved
cluster-autoscaler/cloudprovider/huaweicloud/huaweicloud_service_manager.go
Show resolved
Hide resolved
cluster-autoscaler/cloudprovider/huaweicloud/huaweicloud_service_manager.go
Outdated
Show resolved
Hide resolved
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.
Just a nit, otherwise LGTM.
Thanks.
/lgtm Congrats! For your first PR! Good job! |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: RainbowMango, wangshiqi308 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 |
Just a reminder, it's better to squash your commits when you fix comments. :) |
Implemented TemplateNodeInfo function. TemplateNodeInfo returns a schedulerframework.NodeInfo structure of an empty
(as if just started) node. This will be used in scale-up simulations to predict what would a new node look like if a node group was expanded. The returned NodeInfo is expected to have a fully populated Node object, with all of the labels, capacity and allocatable information as well as all pods that are started on the node by default, using manifest (most likely only kube-proxy).