-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
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
Worker doesn't start when minio enabled #87
Comments
Same issue here: The PVC is still referenced in the lago-worker. And there is no s3/minio configuration in lago-worker when minio is enabled. |
Good catch here sorry about that. PR is on the way Should be good with #89 merge |
what about S3 credentials in worker-deployment if using minio? I would expect S3 environment variables in the worker-deployment just like in api-deployment (lines 148-209):
|
Its now merge & should be good. Feel free to re-open this issue if its doesn't solve. |
When minio enabled, worker is searching for non existing pvc, because there is a missing condition.
Line 179 and 185 in worker-deployment.yaml, instead of
{{ if not .Values.global.s3.enabled }}
can someone just put
{{- if and (not .Values.global.s3.enabled) (not .Values.minio.enabled) }}
The text was updated successfully, but these errors were encountered: