Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Docs] Add sizing recommendation for backend pod #8422

Open
wilfriedroset opened this issue Feb 6, 2023 · 2 comments
Open

[Docs] Add sizing recommendation for backend pod #8422

wilfriedroset opened this issue Feb 6, 2023 · 2 comments
Assignees
Labels
help wanted We would love help on these issues. Please come help us! keepalive An issue or PR that will be kept alive and never marked as stale. type/docs Issues related to technical documentation; the Docs Squad uses this label across many repositories

Comments

@wilfriedroset
Copy link
Contributor

Describe the solution you'd like
The documentation about "size the cluster" could add support for the new SSD chart with the three part deployment. The current version as of now only show write/read.
Example:

loki:
  authenabled: false
read:
  replicas: 75
  resources:
    requests:
      cpu: 3
      memory: 6
    limits:
      cpu: 3
      memory: 8
write:
  replicas: 58
  resources:
    requests:
      cpu: 1
      memory: 6
    limits:
      cpu: 2
      memory: 12

Describe alternatives you've considered
N/A

Additional context
https://grafana.com/docs/loki/next/installation/sizing/

@JStickler JStickler changed the title Add sizing recommendation for backend pod [Docs] Add sizing recommendation for backend pod Feb 6, 2023
@JStickler JStickler added the type/docs Issues related to technical documentation; the Docs Squad uses this label across many repositories label Feb 6, 2023
@wilfriedroset
Copy link
Contributor Author

Please also note that unit must be specified for the memory. Without any, the default will be taken into account. The default unit for memory is byte and we don't want to start with that few memory.

@jeschkies jeschkies added the keepalive An issue or PR that will be kept alive and never marked as stale. label Apr 27, 2023
@JStickler JStickler added the help wanted We would love help on these issues. Please come help us! label Oct 31, 2023
@LeszekBlazewski
Copy link

This would be really helpful!

The docs also don't mention any sizing recommendations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted We would love help on these issues. Please come help us! keepalive An issue or PR that will be kept alive and never marked as stale. type/docs Issues related to technical documentation; the Docs Squad uses this label across many repositories
Projects
None yet
Development

No branches or pull requests

4 participants