Add autoscaled-workerpool demo using HPA and prometheus-adapter on Kind - #576
Merged
Julian Gutierrez Oschmann (juli4n) merged 1 commit intoJul 29, 2026
Merged
Conversation
Luiz Oliveira (laoj2)
requested a review
from Julian Gutierrez Oschmann (juli4n)
July 28, 2026 21:33
Collaborator
|
Needs rebase. |
Luiz Oliveira (laoj2)
force-pushed
the
hpa-demo
branch
from
July 29, 2026 16:11
4dc430d to
5c7e9fe
Compare
Collaborator
Author
Done |
Julian Gutierrez Oschmann (juli4n)
approved these changes
Jul 29, 2026
Julian Gutierrez Oschmann (juli4n)
merged commit Jul 29, 2026
9490650
into
agent-substrate:main
11 checks passed
This file contains hidden or 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
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.
This introduces a new demo (
demos/autoscaled-workerpool) demonstrating how to dynamically autoscale a WorkerPool using HPA +prometheus-adapteron a local Kind cluster.As mentioned in #198, this approach may be too slow for some use cases, but this is a good first milestone.
Plus, there are some limitations with scaling workerpools that still need to be addressed, for example:
Scale-down can strand paused actors. When a worker pod is removed, a local-snapshot paused actor keeps its node pin pointing at a node that may no longer have (free) worker pods.
Scale-up gives no locality guarantee: If there are multiple local-snapshot paused actors that can't resume because no worker pods are available on their node, upscaling will not unblock them: the added capacity can land anywhere, so the pool can grow without ever placing a worker where a stranded actor needs it.
Scale-down picks victims blind to actor assignment (can kill busy pods).
Tests pass: n/a
Appropriate changes to documentation are included in the PR