-
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 216
The lokistack-sample-ingester try to connect to S3 when secret.type=azure.
Step to Reproduce:
1. Deploy Loki-operators
2. Create azure secret.
{
"apiVersion": "v1",
"data": {
"account_key": "example",
"account_name": "example",
"container": "example",
"environment": "QXp1cmVHbG9iYWw="
},
"kind": "Secret",
"metadata": {
"creationTimestamp": "2022-03-17T06:47:52Z",
"name": "azure-secret",
"namespace": "openshift-logging",
"resourceVersion": "157804",
"uid": "99d1afda-0dee-4b98-b60d-758b84b57de3"
},
"type": "Opaque"
}
3. create lokistack resource.
{
"apiVersion": "loki.grafana.com/v1beta1",
"kind": "LokiStack",
"metadata": {
"name": "lokistack-sample"
},
"spec": {
"managementState": "Managed",
"replicationFactor": 2,
"size": "1x.extra-small",
"storage": {
"secret": {
"name": "azure-secret",
"type": "azure"
}
},
"storageClassName": "managed-premium",
"tenants": {
"mode": "openshift-logging"
}
}
}
Actual Result
$ oc logs lokistack-sample-ingester-0
Logs: http://pastebin.test.redhat.com/1037927
- links to
