-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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: release a new helm charts to use k8s service for discover query-scheduler replicas #9477
Merged
sandeepsukhani
merged 2 commits into
grafana:main
from
sandeepsukhani:helm-use-k8s-service-query-scheduler-discovery
May 22, 2023
+73
−2
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
26 changes: 26 additions & 0 deletions
26
production/helm/loki/templates/backend/query-scheduler-discovery.yaml
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,26 @@ | ||
{{- $isSimpleScalable := eq (include "loki.deployment.isScalable" .) "true" -}} | ||
{{- if and $isSimpleScalable (not .Values.read.legacyReadTarget ) }} | ||
--- | ||
apiVersion: v1 | ||
kind: Service | ||
metadata: | ||
name: query-scheduler-discovery | ||
labels: | ||
{{- include "loki.backendSelectorLabels" . | nindent 4 }} | ||
prometheus.io/service-monitor: "false" | ||
spec: | ||
type: ClusterIP | ||
clusterIP: None | ||
publishNotReadyAddresses: true | ||
ports: | ||
- name: http-metrics | ||
port: 3100 | ||
targetPort: http-metrics | ||
protocol: TCP | ||
- name: grpc | ||
port: 9095 | ||
targetPort: grpc | ||
protocol: TCP | ||
selector: | ||
{{- include "loki.backendSelectorLabels" . | nindent 4 }} | ||
{{- end }} |
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -207,6 +207,16 @@ loki: | |
index_gateway: | ||
{{- tpl (. | toYaml) $ | nindent 4 }} | ||
{{- end }} | ||
|
||
{{- with .Values.loki.frontend }} | ||
frontend: | ||
{{- tpl (. | toYaml) $ | nindent 4 }} | ||
{{- end }} | ||
|
||
{{- with .Values.loki.frontend_worker }} | ||
frontend_worker: | ||
{{- tpl (. | toYaml) $ | nindent 4 }} | ||
{{- end }} | ||
# Should authentication be enabled | ||
auth_enabled: true | ||
# Extra memberlist configuration | ||
|
@@ -302,6 +312,10 @@ loki: | |
# -- Optional index gateway configuration | ||
index_gateway: | ||
mode: ring | ||
frontend: | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Alternatively we could add the comment here to set these to empty objects when we bump the Loki version. |
||
scheduler_address: '{{ include "loki.querySchedulerAddress" . }}' | ||
frontend_worker: | ||
scheduler_address: '{{ include "loki.querySchedulerAddress" . }}' | ||
enterprise: | ||
# Enable enterprise features, license must be provided | ||
enabled: false | ||
|
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.
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.
Can we add a TODO or some other note here to remove this section once we bump the Loki version?
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.
What do you think about continuing to use k8s service for service discovery? I am going to merge this PR, for now, to get the fix out. I will take care of the feedback in PR #9471 if you think we should move back to ring-based service discovery.