truthtrap commented on issue #72: URL: https://github.com/apache/pulsar-helm-chart/issues/72#issuecomment-841620773
well, i got it to work. the broker.configData in values.yaml part looks like this ` # tiered storage to gcs` ` managedLedgerOffloadDriver: google-cloud-storage` ` gcsManagedLedgerOffloadBucket: pulsar` ` gcsManagedLedgerOffloadRegion: europe-west1` ` managedLedgerOffloadAutoTriggerSizeThresholdBytes: "262144000"` ` gcsServiceAccountSecret: "pulsar-broker-service-account"` ` gcsServiceAccountJsonFile: "serviceaccount.json"` ` gcsManagedLedgerOffloadServiceAccountKeyFile: "/pulsar/gcp-service-account/serviceaccount.json"` for this to work with the [diff above](https://github.com/apache/pulsar-helm-chart/issues/72#issuecomment-728746553) you need create the service account json as [per the documentation](https://pulsar.apache.org/docs/en/tiered-storage-gcs/). add the resulting json file with the credentials (serviceaccount.json) as a secret to your k8s cluster (make sure to add it to the right namespace) `$ kubectl -n pulsar create secret generic pulsar-broker-service-account --from-file=serviceaccount.json` in case of an existing release, upgrade your helm deployment and roll over your broker statefulset `$ helm upgrade <your-release-name> charts/pulsar` `$ kubectl -n pulsar rollout restart statefulset production-pulsar-broker` -- 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
