troubleshooting
What was the issue with the helm chart deployment into EKS and how was it fixed?
The discussion thread involves an issue with the helm chart deployment into EKS and the subsequent fix that was implemented. The issue was related to a misinterpretation of a boolean value in the helm template.
Do
Dominic Lindsay
Asked on Oct 17, 2023
- The issue with the helm chart deployment into EKS was caused by the helm template misinterpreting a boolean value.
- The fix involved updating the helm template to correctly interpret the boolean value.
- The version containing the fix is
0.1.24.
- The helm template mistakenly treated the boolean value as a string:
{{- define "risingwave.credentialsSecretRequired" -}}
{{- if and .Values.stateStore.s3.enabled (not .Values.stateStore.s3.authentication.useServiceAccount) }}
true
{{- else if and (not .Values.tags.minio) .Values.stateStore.minio.enabled }}
true
{{- else if and .Values.stateStore.oss.enabled (not .Values.stateStore.oss.authentication.useServiceAccount) }}
true
{{- else if and .Values.stateStore.gcs.enabled (not .Values.stateStore.gcs.authentication.useServiceAccount) }}
true
{{- else if and .Values.stateStore.azblob.enabled (not .Values.stateStore.azblob.authentication.useServiceAccount) }}
true
{{- else }}
false
{{- end }}
{{- end }}Oct 18, 2023Edited by