You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{- define "quickwit.environment" -}}
....
- name: QW_CLUSTER_ENDPOINT
value: http://{{ include "quickwit.fullname" $ }}-metastore.{{ $.Release.Namespace }}.svc.cluster.local:7280
{{- range $key, $value := .Values.environment }}
- name: "{{ $key }}"
value: "{{ $value }}"
{{- end }}
{{- end }}
Which hardcodes the cluster name as cluster.local which is not always the case, and so Quickwit doesn't work in clusters with non-default name.
It's impossible to override the value by specifying an .environment because Kubernetes takes the first value in the env list. So, right now it allows only to append a variable.
I see at least 3 ways how it can be fixed:
Allows to set the cluster name. That's probably most common in other charts
Do not use the cluster name at all http://{{ include "quickwit.fullname" $ }}-metastore.{{ $.Release.Namespace }}:7280 would suffice since it's not supposed to connect to an endpoint in another cluster.
Move the last part (i..e, the range loop) to the top, which would allow to update any environment variable, not just append.
The text was updated successfully, but these errors were encountered:
In
_helpers.tpl
there is the following lines:Which hardcodes the cluster name as
cluster.local
which is not always the case, and so Quickwit doesn't work in clusters with non-default name.It's impossible to override the value by specifying an
.environment
because Kubernetes takes the first value in theenv
list. So, right now it allows only to append a variable.I see at least 3 ways how it can be fixed:
http://{{ include "quickwit.fullname" $ }}-metastore.{{ $.Release.Namespace }}:7280
would suffice since it's not supposed to connect to an endpoint in another cluster.range
loop) to the top, which would allow to update any environment variable, not just append.The text was updated successfully, but these errors were encountered: