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

Fix when extraflags for thanos components were overridden #99

Closed
wants to merge 1 commit into from

Conversation

michal-gubricky
Copy link
Member

This commit fixes the scenario when settings for thanos components, which are set via extra flags in values.yaml was overridden by values in a multicluster-config folder.

This commit fixes the scenario when settings for thanos components
set via extra flags in values.yaml was overridden
by values in a multicluster-config folder.

Signed-off-by: michal.gubricky <[email protected]>
"max_size": "500MB"
"max_size_items": 0
"validity": 0s
"type": "in-memory"
Copy link
Member

Choose a reason for hiding this comment

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

IMO we should keep these extraFlags here.
IMO we should support the scenario when the end-user uses the base values and overrides some parameters like queryFrontend.enabled=True, then the end user should end with extraFlags we set for queryFrontend

retentionResolution1h: 15d
extraFlags:
- --compact.concurrency=3
- --downsample.concurrency=3
Copy link
Member

Choose a reason for hiding this comment

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

@@ -52,7 +52,19 @@ thanos:
existingObjstoreSecret: thanos-objstore-config
queryFrontend:
enabled: true
extraFlags:
Copy link
Member

@matofeder matofeder Feb 23, 2024

Choose a reason for hiding this comment

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

IMO this file should be used as a values file which should override the default values file:

  • helm install .... -f multicluster-config/observer-values.yaml

then I do not think that these changes are necessary

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