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 feedback: https://grafana.com/docs/loki/latest/setup/size/ is COMPLETELY broken #12618

Closed
simonfelding opened this issue Apr 15, 2024 · 4 comments
Labels
type/docs Issues related to technical documentation; the Docs Squad uses this label across many repositories

Comments

@simonfelding
Copy link

simonfelding commented Apr 15, 2024

Hi Grafana
The values output here are completely broken and cause the deployment to fail with very bad error messages. Please take the link down or fix the output.

It produces the following output (as an example):

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

Problems:

  1. It returns a file that does not end with yaml.
  2. The output is not complete: You need to add more to get it working.
  3. EXTREMELY BAD: The resources do not have units. This causes Kubernetes to break, as it assumes the units are very small.

It results in errors like
Warning FailedMount 18m kubelet MountVolume.SetUp failed for volume "kube-api-access-fl7vf" : write /var/lib/kubelet/pods/ed8cd4f9-ad9f-448a-a2e9-7891dfff649a/volumes/kubernetes.io~projected/kube-api-access-fl7vf/..2024_04_15_13_43_31.1659629596/ca.crt: no space left on device

Because Kubernetes uses the memory limits for the projected volume too.

@JStickler JStickler added the type/docs Issues related to technical documentation; the Docs Squad uses this label across many repositories label Apr 15, 2024
@JStickler
Copy link
Contributor

@simonfelding, thanks for the feedback, someone also reported a different issue last Friday with the values that were being generated, and after some discussion with the Engineering team and leadership, we've decided to pull the sizing calculator for the time being. See #12598.

@ThaoLe366
Copy link

ThaoLe366 commented May 28, 2024

@JStickler
Hi, do we have any updates on the calculator? It appears to have issues with the units or formulas. I want to determine how much CPU and disk space.... my system requires, but I can't find any information

@JStickler
Copy link
Contributor

The calculator is probably not going to be republished. The engineering team does not have the cycles to update it.

@ThaoLe366
Copy link

Thank you for your response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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

3 participants