Open yskopets opened 3 months ago
Apparently, the issue was caused by an explicit value for the endpoint
field:
loki:
storage:
type: s3
s3:
endpoint: s3.us-east-2.amazonaws.com
Well, it's confusing.
I took configuration snippet
endpoint: s3.us-east-2.amazonaws.com
from Mimir documentation - https://grafana.com/docs/helm-charts/mimir-distributed/latest/run-production-environment-with-helm/#configure-mimir-to-use-object-storage
Do Loki and Mimir need different values for the endpoint
field?
Is it not a good idea, after all, to set an explicit value for the endpoint
field?
I took configuration snippet endpoint: s3.us-east-2.amazonaws.com from Mimir documentation
Are you actually setting up your AWS in the United States? Your GitHub profile says you're in the Netherlands, I would have thought your AWS would be located somewhere in Europe? The value for endpoint
should be YOUR endpoint, which is not necessarily going to match the example in the docs.
Describe the bug
This is the entire Pod log. Loki container fails to start.
To Reproduce Steps to reproduce the behavior:
Expected behavior The error should clearly state what part of the config causes it.
Environment:
Screenshots, Promtail config, or terminal output If applicable, add any output to help explain your problem.