-
Story
-
Resolution: Done
-
Undefined
-
None
-
None
-
5
-
False
-
False
-
-
NetObserv - Sprint 221, NetObserv - Sprint 222, NetObserv - Sprint 223, NetObserv - Sprint 224
Loki operator actually deploys loki stack + gateway
For now, we directly point distributor to write kube-enricher logs
We need figure out how loki stack will be secured on loki operator side + choose between writing directly to distributor or through the gateway using a service account (not yet implemented)
- is blocked by
-
NETOBSERV-34 Deploy our stack with the Loki Operator
- Closed
- is related to
-
NETOBSERV-98 Loki auth on the query side
- Closed
-
NETOBSERV-473 Loki and strimzi operator installation
- Closed
-
NETOBSERV-489 Use console-plugin authorize API
- Closed
-
NETOBSERV-561 Loki Operator gateway query parsing
- Closed
-
NETOBSERV-486 update loki config for performance tests
- Closed
- relates to
-
NETOBSERV-43 [R&D and/or impl] Multi-tenancy support
- Closed
-
NETOBSERV-424 POC: use loki-operator gateway to enable loki multi tenancy
- Closed
- links to
- mentioned on