Open ericmeadows opened 1 year ago
We're also hitting this issue now where GCS storage doesn't work despite configuring it with the helm chart for loki.
loki-write-0 loki level=error ts=2023-05-05T04:20:32.131662407Z caller=flush.go:144 org_id=fake msg="failed to flush" err="failed to flush chunks: store put chunk: NoCredentialProviders: no valid providers in chain. Deprecated.\n\tFor verbose messaging see aws.Config.CredentialsChainVerboseErrors, num_chunks: 1, labels: {app=\"host-scanner\", container=\"host-sensor\", filename=\"/var/log/pods/kubescape-host-scanner_host-scanner-knpc7_1d9d6c80-9edf-4011-9e6f-1d0cf^Cloki-write-0 loki level=error ts=2023-05-05T04:20:32.131858327Z caller=flush.go:144 org_id=fake msg="failed to flush" err="failed to flush chunks: store put chunk: NoCredentialProviders: no valid providers in chain. Deprecated.\n\tFor verbose messaging see aws.Config.CredentialsChainVerboseErrors, num_chunks: 1, labels: {app=\"app-name-redacted\", container=\"cloudsql-proxy\", filename=\"/var/log/pods/default_app-name-redacted-55d5f987cd-kd2st_5c0a8d7d-1abe-4b8a-bbcf-e38439c68828/cloudsql-proxy/0.log\", instance=\"app-name-redacted\", job=\"default/app-name-redacted\", namespace=\"default\", node_name=\"gke-dev-t2d-preemptible--badd0736-g2f5\", pod=\"app-name-redacted-55d5f987cd-kd2st\", stream=\"stderr\"}"
We're also hitting this issue now where GCS storage doesn't work despite configuring it with the helm chart for loki.
loki-write-0 loki level=error ts=2023-05-05T04:20:32.131662407Z caller=flush.go:144 org_id=fake msg="failed to flush" err="failed to flush chunks: store put chunk: NoCredentialProviders: no valid providers in chain. Deprecated.\n\tFor verbose messaging see aws.Config.CredentialsChainVerboseErrors, num_chunks: 1, labels: {app=\"host-scanner\", container=\"host-sensor\", filename=\"/var/log/pods/kubescape-host-scanner_host-scanner-knpc7_1d9d6c80-9edf-4011-9e6f-1d0cf^Cloki-write-0 loki level=error ts=2023-05-05T04:20:32.131858327Z caller=flush.go:144 org_id=fake msg="failed to flush" err="failed to flush chunks: store put chunk: NoCredentialProviders: no valid providers in chain. Deprecated.\n\tFor verbose messaging see aws.Config.CredentialsChainVerboseErrors, num_chunks: 1, labels: {app=\"app-name-redacted\", container=\"cloudsql-proxy\", filename=\"/var/log/pods/default_app-name-redacted-55d5f987cd-kd2st_5c0a8d7d-1abe-4b8a-bbcf-e38439c68828/cloudsql-proxy/0.log\", instance=\"app-name-redacted\", job=\"default/app-name-redacted\", namespace=\"default\", node_name=\"gke-dev-t2d-preemptible--badd0736-g2f5\", pod=\"app-name-redacted-55d5f987cd-kd2st\", stream=\"stderr\"}"
Did you find a solution? @AgrimPrasad
Having the same issue with azure storage
We updated to latest grafana and loki versions and the gcs bug was fixed there
We updated to latest grafana and loki versions and the gcs bug was fixed there
Can you please share the configuration you've applied, and which version (Loki + Loki helm chart) works ?
Describe the bug I installed Loki using the 5.0.0 Helm Chart, using GCS as my
storage.type
, but it does not work.As an aside, if feels like the documentation surrounding GCS is lacking.
To Reproduce Steps to reproduce the behavior:
Expected behavior Loki to spin up and store objects in our GCS bucket.
Environment:
Screenshots, Promtail config, or terminal output