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

Loki Simple Scalable Tutorial Not Working - pod has unbound immediate PersistentVolumeClaims #14892

Open
shreybatra opened this issue Nov 13, 2024 · 1 comment
Labels
area/helm type/bug Somehing is not working as expected

Comments

@shreybatra
Copy link

Describe the bug
While trying to deploy Loki with Helm charts using the given official tutorial, and using s3 as the object store in Simple Scalable mode, the backend and chunks-cache pods are stuck in Pending state with error -

pod has unbound immediate PersistentVolumeClaims. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling.

The PVCs when found are using storage class hostpath -

test-logging   data-loki-write-0   Pending                                      hostpath       <unset>                 19s
test-logging   data-loki-write-1   Pending                                      hostpath       <unset>                 19s
test-logging   data-loki-write-2   Pending                                      hostpath       <unset>                 19s

Values config file -

loki:
  schemaConfig:
    configs:
      - from: "2024-04-01"
        store: tsdb
        object_store: s3
        schema: v13
        index:
          prefix: loki_index_
          period: 24h
  storage_config:
    aws:
      region: ap-south-1
      bucketnames: <my bucket name>
      s3forcepathstyle: false
  pattern_ingester:
      enabled: true
  limits_config:
    allow_structured_metadata: true
    volume_enabled: true
    retention_period: 672h # 28 days retention
  querier:
    max_concurrent: 4

  storage:
    type: s3
    bucketNames:
        chunks: <my bucket name>
        ruler: <my bucket name>
        admin: <my bucket name>
    s3:
      # AWS endpoint URL
      endpoint: s3.ap-south-1.amazonaws.com
      # AWS region where the S3 bucket is located
      region: ap-south-1
      # AWS secret access key
      secretAccessKey: <secret, which is url encoded>
      # AWS access key ID
      accessKeyId: <access id>
      s3ForcePathStyle: false
      insecure: false

deploymentMode: SimpleScalable

backend:
  replicas: 1
read:
  replicas: 1
write:
  replicas: 1

# Disable minio storage
minio:
  enabled: false

To Reproduce
Steps to reproduce the behavior:

  1. Started Loki (SHA or version)

Environment:

  • Tried on local K8s as well as a testing EKS cluster on AWS.
@daimalou
Copy link

daimalou commented Nov 13, 2024

The official documentation is outdated and full of flaws, and it seems that no one is maintaining it.

The Loki documentation is the worst documentation I've ever seen.

The Loki documentation lacks examples and only provides configurations, leaving people to guess how to use it.

In the past couple of days, I deployed Loki on Docker and encountered numerous issues. The official documentation is outdated. Even though the official documentation is supposed to be the latest version (V3), the docker-compose.yaml provided in the official documentation uses old images(V2).

I suspect they intentionally don't maintain the documentation so that you have to buy their services to get your questions answered.

@JStickler JStickler added area/helm type/bug Somehing is not working as expected labels Nov 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/helm type/bug Somehing is not working as expected
Projects
None yet
Development

No branches or pull requests

3 participants