Details
-
Bug
-
Resolution: Done
-
Undefined
-
Logging 5.4.0
-
False
-
None
-
False
-
NEW
-
OBSDA-7 - Adopting Loki as an alternative to Elasticsearch to support more lightweight, easier to manage/operate storage scenarios
-
VERIFIED
-
Logging (LogExp) - Sprint 217, Logging (LogExp) - Sprint 218, Logging (LogExp) - Sprint 219
Description
There isn't an authentication mechanism in the provided Loki configuration. The Loki GCS authentication is handled via the GCS SDK which is typically done with environment variables(For example:GOOGLE_APPLICATION_CREDENTIALS).
Refer to https://stackoverflow.com/questions/65232062/can-i-setup-a-single-store-on-gcs-and-have-multiple-local-instances-of-loki-read.
The loki-operator should provide a method to handle GCS authentication. we can refer to docker registry which supports various Objective Storage too. It uses REGISTRY_STORAGE_GCS_KEYFILE to get authenticated from GCP. Refer to https://docs.openshift.com/container-platform/4.10/registry/configuring_registry_storage/configuring-registry-storage-gcp-user-infrastructure.html