DonghunLouisLee commented on issue #72:
URL:
https://github.com/apache/pulsar-helm-chart/issues/72#issuecomment-728746553
> As a comment, for GCS it did not work just adding
>
> `broker: configData: managedLedgerOffloadDriver: google-cloud-storage
gcsManagedLedgerOffloadBucket: pulsar-tiered gcsManagedLedgerOffloadRegion:
us-east1 managedLedgerOffloadAutoTriggerSizeThresholdBytes: "262144000"`
>
> because it was lacking the service account key file, which needs to be
mounted. I added by hand in the statefulset of the broker the following volumes
and volumeMounts and worked adding a field:
>
> ```
> gcsManagedLedgerOffloadServiceAccountKeyFile:
"/pulsar/gcp-service-account/{{
.Values.broker.configData.gcsServiceAccountJsonFile }}"
> ```
>
> ```
> +++ b/charts/pulsar/templates/broker-statefulset.yaml
> @@ -225,7 +225,19 @@ spec:
> {{- end }}
> {{- end }}
> {{- include "pulsar.broker.certs.volumeMounts" . | nindent 10 }}
> + {{- if .Values.broker.configData.managedLedgerOffloadDriver }}
> + {{- if eq .Values.broker.configData.managedLedgerOffloadDriver
"google-cloud-storage" }}
> + - name: gcp-service-account
> + readOnly: true
> + mountPath: /pulsar/gcp-service-account
> + {{- end }}
> + {{- end }}
> volumes:
> + {{- if eq .Values.broker.configData.managedLedgerOffloadDriver
"google-cloud-storage" }}
> + - name: gcp-service-account
> + secret:
> + secretName: {{
.Values.broker.configData.gcsServiceAccountSecret }}
> + {{- end }}
> {{- if .Values.auth.authentication.enabled }}
> {{- if eq .Values.auth.authentication.provider "jwt" }}
> - name: token-keys
> ```
is it possible to know how you applied the new
b/charts/pulsar/templates/broker-statefulset.yaml? did you use helm upgrade?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
