helm: Make query-scheduler a required component #12188
Draft
Conversation
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
56quarters
force-pushed
the
56quarters/scheduler-helm
branch
from
aa30bc2 to
e7a5623
Compare
This change always configures the query-frontend and querier workers to use the query-scheduler. Part of #11884 Signed-off-by: Nick Pillitteri <[email protected]>
56quarters
force-pushed
the
56quarters/scheduler-helm
branch
from
e7a5623 to
b573139
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 this PR does
This change always configures the query-frontend and querier workers to use the query-scheduler.
Which issue(s) this PR fixes or relates to
Part of #11884
Note for reviewers
Every component in the helm chart has an
enabledsetting that can be used to prevent its manifests from being rendered. I didn't remove this from the query-scheduler since all other components (which are required) still have it. I did however not make configuration ofscheduler-addressdepend on its setting when rendering the configuration file.Checklist
CHANGELOG.mdupdated - the order of entries should be[CHANGE],[FEATURE],[ENHANCEMENT],[BUGFIX]. If changelog entry is not needed, please add thechangelog-not-neededlabel to the PR.about-versioning.mdupdated with experimental features.