Skip to content

Conversation

friedrichg
Copy link
Member

What this PR does: Fix default affinity overrides-exporter

Which issue(s) this PR fixes:
Fixes #556

Checklist

  • CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX], [DEPENDENCY]

@friedrichg friedrichg force-pushed the fix-affinity-overrides-exporter branch from 73cff47 to cddac59 Compare September 2, 2025 21:00
@@ -1068,7 +1068,7 @@ overrides_exporter:
- key: app.kubernetes.io/component
operator: In
values:
- query-scheduler
- overrides-exporter
Copy link
Collaborator

Choose a reason for hiding this comment

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

Since overrides-exporter is a singleton, there's so sense in setting anti-affinity with itself. It would make more sense to default to empty affinity, affinity: {}

Copy link
Member Author

Choose a reason for hiding this comment

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

a singleton means I can lose metrics if the component is getting rescheduled. I can't afford that

Signed-off-by: Friedrich Gonzalez <[email protected]>
@friedrichg friedrichg changed the title Fix default affinity overrides-exporter Fix default affinity overrides-exporter & improve overrides exporter chart Sep 2, 2025
Signed-off-by: Friedrich Gonzalez <[email protected]>
@friedrichg friedrichg force-pushed the fix-affinity-overrides-exporter branch from 247df99 to 86f4e5f Compare September 2, 2025 22:10
@friedrichg friedrichg merged commit ae81454 into master Sep 2, 2025
2 checks passed
@friedrichg friedrichg deleted the fix-affinity-overrides-exporter branch September 2, 2025 23:23
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.

overrrides has the wrong default affinity
2 participants