-
Feature
-
Resolution: Done
-
Critical
-
Logging 6.0
-
None
-
False
-
None
-
False
-
Not Selected
-
0
-
0% To Do, 0% In Progress, 100% Done
Proposed title of this feature request
Support sizes smaller than 1x.extra-small in LOKI.
What is the nature and description of the request?
Support the following size smaller than 1x.extra-small in LOKI.
1x.new-spec Data transfer 100GB/day Queries per second (QPS) 1-25 QPS at 200ms Replication factor 2 Total CPU requests 5 vCPUs Total CPU requests if using the ruler 5.5 vCPUs Total memory requests 20Gi Total memory requests if using the ruler 21Gi Total disk requests 430Gi Total disk requests if using the ruler 450Gi
Why does the customer need this? (List the business requirements)
Loki's current resource (CPU/Memory) requirement is too big even with extra-small.spec[1].
It prevents existing customers from migrating their EFK to the Loki/Vector stack.
We could lose many customers if we cannot support a less resource-intensive environment.
Loki itself is a product that was designed to reduce resource consumption compared with EFK or other logging products.
So it's weird why Red Hat's Loki requires more resources than EFK.
Because Red Hat had already announced the removal of EFK[2], there is not much time to wait.
List any affected packages or components.
Logging 6.0 / Loki