-
Notifications
You must be signed in to change notification settings - Fork 79
Conversation
Great @islinwb It looks promising though it's still WIP - it's a good start point. We are looking forward to seeing your PR to firmament as well :) |
/assign |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: islinwb Assign the PR to them by writing 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 |
Should we merge the firmament changes first? |
@m1093782566 Yes. The added e2e test case can pass only after merging huawei-cloudnative/firmament#3. |
pkg/k8sclient/nodewatcher.go
Outdated
@@ -106,6 +106,9 @@ func (nw *NodeWatcher) parseNode(node *v1.Node, phase NodePhase) *Node { | |||
memCap, _ := memCapQuantity.AsInt64() | |||
memAllocQuantity := node.Status.Allocatable[v1.ResourceMemory] | |||
memAlloc, _ := memAllocQuantity.AsInt64() | |||
podCapQuantity := node.Status.Capacity[v1.ResourcePods] |
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's never really used by firmament?
pkg/k8sclient/nodewatcher.go
Outdated
@@ -115,6 +118,8 @@ func (nw *NodeWatcher) parseNode(node *v1.Node, phase NodePhase) *Node { | |||
CPUAllocatable: cpuAllocQuantity.MilliValue(), | |||
MemCapacityKb: memCap / bytesToKb, | |||
MemAllocatableKb: memAlloc / bytesToKb, | |||
PodCapacity: podCapQuantity.Value(), |
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's never really used by firmament? We just pass the PodAllocatable
to firmament?
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.
@m1093782566 Only use PodAllocatable
now. I'll check whether PodCapacity
should be used.
@islinwb Thanks for the PR. For the E2E i would suggest to create an image and upload it here, with a tag like Also shouldn't the test case modify capacity for nodes and check, i don't know if an update to node will set the capacity, or one needs to restart the Because what i understands from the k8s documentation, the max pods limit is set at the time of bringing up the node, and later changes we need to restart the If the later case is true, where we have to restart the nodes agent to make the capacity change. |
1e22c74
to
78da596
Compare
@shivramsrivastava @m1093782566 I've tested in my local VM with the modified Firmament code and the kubelet flag max-pods works. |
We don't need to consider other scheduler for the time being. |
/test ci-poseidon-e2e-gce |
@islinwb: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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/test-infra repository. I understand the commands that are listed here. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
for #88
Firmament part: huawei-cloudnative/firmament#3