-
Notifications
You must be signed in to change notification settings - Fork 550
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
helm: add enabled
field for admin-api,compactor,distributor,gateway,ingester,querier,query-frontend,store-gateway
#9734
helm: add enabled
field for admin-api,compactor,distributor,gateway,ingester,querier,query-frontend,store-gateway
#9734
Conversation
instrumentation: | ||
enabled: false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
now this is automatically set up
@@ -10,7 +10,7 @@ compactor: | |||
ingester: | |||
schedulerName: my-scheduler | |||
|
|||
store-gateway: | |||
store_gateway: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
unrelated to the PR, but it's wrong test config which i noticed
{{- if .Values.distributor.enabled }} | ||
distributor: | ||
url: dns:///{{ template "mimir.fullname" . }}-distributor-headless.{{ .Release.Namespace }}.svc.{{ .Values.global.clusterDomain }}:{{ include "mimir.serverGrpcListenPort" . }} | ||
{{- end }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the gateway would try to resolve the dns:///
address before starting. Since it's not there, we shouldn't set it up.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall LGTM.
Do we still need the gossip-ring
service when deploying the federation-frontend? Same question for the runtime ConfigMap.
technically the FF doesn't use either, but it keeps the config consistent with other components. I guess that's not a good enough reason. I'll remove them along with the update: they're disabled in eda445e most of the disableOtherComponents work is done in 6a4f68e |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM modulo question about outdated comment below
...ons/helm/charts/mimir-distributed/ci/offline/test-enterprise-federation-frontend-values.yaml
Outdated
Show resolved
Hide resolved
Signed-off-by: Dimitar Dimitrov <[email protected]>
Signed-off-by: Dimitar Dimitrov <[email protected]>
Signed-off-by: Dimitar Dimitrov <[email protected]>
Signed-off-by: Dimitar Dimitrov <[email protected]>
Signed-off-by: Dimitar Dimitrov <[email protected]>
Signed-off-by: Dimitar Dimitrov <[email protected]>
Signed-off-by: Dimitar Dimitrov <[email protected]>
Signed-off-by: Dimitar Dimitrov <[email protected]>
Signed-off-by: Dimitar Dimitrov <[email protected]>
Signed-off-by: Dimitar Dimitrov <[email protected]>
Signed-off-by: Dimitar Dimitrov <[email protected]>
Co-authored-by: Charles Korn <[email protected]>
Signed-off-by: Dimitar Dimitrov <[email protected]>
Signed-off-by: Dimitar Dimitrov <[email protected]>
eda445e
to
13cd3b6
Compare
Signed-off-by: Dimitar Dimitrov <[email protected]>
Signed-off-by: Dimitar Dimitrov <[email protected]>
299a2b1
to
383dca1
Compare
This reverts commit 383dca1.
What this PR does
This adds
enabled
flag for a few components which are normally required for a Mimir/GEM deployment. We need this so that deploying the federation-frontend doesn't end up deploying a ton of unrelated and unnecessary resources.federation_frontend.disableOtherComponents
to have the same effect as settingenabled: false
on all components.I've also disabled them in the rendered federation-frontend values. Now all the files when rendering the federation-frontend are these:
Which issue(s) this PR fixes or relates to
Related to #9672
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]
.about-versioning.md
updated with experimental features.