Skip to content
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

refactor(runtime): make topologySpread configurable #643

Merged
merged 1 commit into from
Oct 16, 2024

Conversation

hspedro
Copy link
Collaborator

@hspedro hspedro commented Oct 15, 2024

Read the TopologySpreadConstraints maxSkew, topologyKey, and whenUnsatisfiable from the YAML config so we can tune based on cluster/game. By default, it will be set to 5. Using a low value leads to underutilized nodes which impacts in cost

Copy link
Collaborator

@joaobologna joaobologna left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@hspedro hspedro changed the title refactor(runtime): make maxSkew configurable refactor(runtime): make topologySpread configurable Oct 15, 2024
@hspedro hspedro force-pushed the fix/maxSkew-configurable branch 4 times, most recently from 3b84d2f to 5e985aa Compare October 15, 2024 19:54
Read the TopologySpreadConstraints config from the YAML config
so we can tune based on cluster/game. By default it will be enabled.
Using a low value for maxSkew leads to underutilized nodes which
impacts in cost.
@hspedro hspedro merged commit 9682f8f into main Oct 16, 2024
12 checks passed
@hspedro hspedro deleted the fix/maxSkew-configurable branch October 16, 2024 12:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants