[noderesourcetopology] update NRT when attributes change #631
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
k8s-ci-robot
added
do-not-merge/work-in-progress
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ffromani 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 |
k8s-ci-robot
added
the
cncf-cla: yes
✅ Deploy Preview for kubernetes-sigs-scheduler-plugins canceled.
|
k8s-ci-robot
added
approved
ffromani
force-pushed
the
handle-attribute-updates
branch
2 times, most recently
from
020fa0f
to
30dd0d7
Compare
k8s-ci-robot
added
size/XL
ffromani
force-pushed
the
handle-attribute-updates
branch
2 times, most recently
from
bb78532
to
8320fa2
Compare
ffromani
force-pushed
the
handle-attribute-updates
branch
from
8320fa2
to
c3390ce
Compare
k8s-ci-robot
added
the
needs-rebase
ffromani
force-pushed
the
handle-attribute-updates
branch
from
c3390ce
to
f2477f6
Compare
k8s-ci-robot
removed
the
needs-rebase
ffromani
force-pushed
the
handle-attribute-updates
branch
from
f2477f6
to
53cd272
Compare
k8s-ci-robot
added
the
needs-rebase
ffromani
force-pushed
the
handle-attribute-updates
branch
from
53cd272
to
0d6a82b
Compare
k8s-ci-robot
removed
the
needs-rebase
k8s-ci-robot
added
the
needs-rebase
ffromani
force-pushed
the
handle-attribute-updates
branch
from
0d6a82b
to
0d4a769
Compare
k8s-ci-robot
removed
the
needs-rebase
ffromani
force-pushed
the
handle-attribute-updates
branch
2 times, most recently
from
b764751
to
46fd5c8
Compare
A upcoming change in the overreserve cache wants to consume nodeconfig utilities, so in order to enable both packages to consume this code, we move it in its own package. Trivial code movement and only necessary interface changes (renames/public <-> private symbols). Signed-off-by: Francesco Romani <fromani@redhat.com>
create and require watchable client. The watchable client is fully supported by the controller-runtime client and it's a superset of the regular client, so this change is fully backward compatible. Signed-off-by: Francesco Romani <fromani@redhat.com>
In the NodeResourceTopologyMatch plugin we only need to consume resources, never to change them. So let's use a Reader instead of a full client. Signed-off-by: Francesco Romani <fromani@redhat.com>
ffromani
force-pushed
the
handle-attribute-updates
branch
2 times, most recently
from
84394a7
to
0d31c28
Compare
k8s-ci-robot
added
size/XXL
ffromani
force-pushed
the
handle-attribute-updates
branch
2 times, most recently
from
76531af
to
910b12b
Compare
|
the integration test is pretty much done but thare are known issues I'm investigating. |
ffromani
force-pushed
the
handle-attribute-updates
branch
2 times, most recently
from
f16f925
to
8072fc4
Compare
ffromani
changed the title
k8s-ci-robot
removed
the
do-not-merge/work-in-progress
|
/cc @Tal-or |
ffromani
force-pushed
the
handle-attribute-updates
branch
from
8072fc4
to
2afceb1
Compare
ffromani
changed the title
One of the key assumptions we took when designing the NodeResourceTopology (NRT) plugin is that the kubelet configuration of the worker node changes *very* rarely, if at all, during the cluster lifetime. As rule of thumb, it was expected to change with a frequency of like once every quarter (3 months) or so, and likely less often. So the event of changing during a scheduling cycle was deemed extremely low. However, we fail to notice kubelet configuration changes (the bits we care reported by NRT data) and we update them incidentally when resyncing the cache. These updates are expected to be rare, but still failing to noticing them is a much worse issue: with out of date configuration information, the scheduler plugin will take wrong decisions until restarted. Up until now, the mitigation was to restart the scheduler once kubelet config changes; this works, but it is unpractical and requires more orchestration. We add the option to resync the NRT data if the attribute change (and nothing else did) to overcome this limitation. In the current framework, because of how controller-runtime/client works, this will require a new connection to the apiserver to watch the changes and react to them, adding the node to the set of the one being resynced in the next resync iteration. Even considering HA scheduler scenarios, this will cause a very limited amount of new connections, and should not cause any scalability concern. Nevertheless, we make the feature opt-in. Signed-off-by: Francesco Romani <fromani@redhat.com>
ffromani
force-pushed
the
handle-attribute-updates
branch
from
2afceb1
to
78e8c3e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
/kind bug
What this PR does / why we need it:
One of the key assumptions we took when designing the NodeResourceTopology (NRT) plugin is that the kubelet config of the worker node changes VERY rarely, if at all, during the cluster lifetime. As rule of thumb, it was expected to change with a frequency of like once every quarter (3 months) or so, and likely less often. So the event of changing during a scheduling cycle was deemed extremely low.
However, we fail to notice kubelet configuration changes (the bits we care reported by NRT data) and we update them incidentally when resyncing the cache.
These updates are expected to be rare, but still failing to noticing them is a different issue because it can lead to unnecessarily bad scheduling decision.
Simply put, failing to noticing these updates is a gap, which we address with this PR
Which issue(s) this PR fixes:
Fixes #621
Special notes for your reviewer:
still WIP, more test ongoing and upcoming
Does this PR introduce a user-facing change?