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

Add runner=true label to matchedExpressions in podAntiAffinity #170

Merged
merged 1 commit into from
Dec 3, 2022

Conversation

cmergenthaler
Copy link
Contributor

@cmergenthaler cmergenthaler commented Nov 23, 2022

Hi,
this PR fixes scheduling of starter-Pod when using spec.separater=true by adding runner=true to matched Label-Expressions in podAntiAffinity.

Fixes #168

Copy link
Contributor

@javaducky javaducky left a comment

Choose a reason for hiding this comment

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

Thank you @cmergenthaler, this is awesome!

I was able to recreate the original issue where the starter pod was unable to start because all nodes had a runner deployed. Having applied the patch, the starter pod could run on any node having a runner pod assigned.

@yorugac yorugac merged commit 175447d into grafana:main Dec 3, 2022
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.

k6.spec.separate also applies affinity to starter-pod
3 participants