We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I am using version 1.4.3 of dapr/dapr, and I have noticed that the Dapr dashboard char does not respect the global registry value in values.yaml.
1.4.3
dapr/dapr
values.yaml
Similar to, e.g., dapr-sentry, dapr-dashboard should also pick the global.registry value from values.yaml.
dapr-sentry
dapr-dashboard
global.registry
The current deployment template (for dapr-dashboard) reads as below:
- name: dapr-dashboard image: "{{ .Values.image.registry }}/{{ .Values.image.name }}:{{ .Values.image.tag }}" imagePullPolicy: {{ .Values.global.imagePullPolicy }}
Perhaps, it should read instead (cheating from dapr-sentry's deployment template):
{{- if contains "/" .Values.image.name }} image: "{{ .Values.image.name }}" {{- else }} image: "{{ .Values.global.registry }}/{{ .Values.image.name }}:{{ .Values.image.tag }}" {{- end }}
Cc: @baboune
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Current Behavior
I am using version
1.4.3
ofdapr/dapr
, and I have noticed that the Dapr dashboard char does not respect the global registry value invalues.yaml
.Desired Behavior
Similar to, e.g.,
dapr-sentry
,dapr-dashboard
should also pick theglobal.registry
value fromvalues.yaml
.Possible Fix
The current deployment template (for
dapr-dashboard
) reads as below:Perhaps, it should read instead (cheating from
dapr-sentry
's deployment template):Cc: @baboune
The text was updated successfully, but these errors were encountered: