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-read pod isnt running because of failed readiness probe #15180

Open
arattanpal opened this issue Nov 28, 2024 · 0 comments
Open

loki-read pod isnt running because of failed readiness probe #15180

arattanpal opened this issue Nov 28, 2024 · 0 comments
Labels
area/helm type/bug Somehing is not working as expected

Comments

@arattanpal
Copy link

arattanpal commented Nov 28, 2024

Describe the bug
I am installing helm chart loki-6.16.0 (also tried the latest) version. All pods seem to be running except loki-read which when i describe has an error "Readiness probe failed: HTTP probe failed with statuscode: 503". I am using Azure blob for storage. I am installing helm chart in "loki" namespace.

values.yaml

loki:
  schemaConfig:
    configs:
      - from: "2024-04-01"
        store: tsdb
        object_store: azure
        schema: v13
        index:
          prefix: loki_index_
          period: 24h
  ingester:
    chunk_encoding: snappy
  tracing:
    enabled: true
  querier:
    max_concurrent: 4

  storage:
    type: azure
    azure:
      # Name of the Azure Blob Storage account
      accountName: "storage_account_name"
      # Key associated with the Azure Blob Storage account
      accountKey: "sas_key"
      # Comprehensive connection string for Azure Blob Storage account (Can be used to replace endpoint, accountName, and accountKey)
      #connectionString: <your-connection-string>
      # Flag indicating whether to use Azure Managed Identity for authentication
      useManagedIdentity: false
      # Flag indicating whether to use a federated token for authentication
      useFederatedToken: false
      # Client ID of the user-assigned managed identity (if applicable)
      #userAssignedId: <your-user-assigned-id>
      # Timeout duration for requests made to the Azure Blob Storage account (in seconds)
      requestTimeout: 120
      # Domain suffix of the Azure Blob Storage service endpoint (e.g., core.windows.net)
      endpointSuffix: blob.core.windows.net
    bucketNames:
      chunks: "chunks"
      ruler: "ruler"
      admin: "admin"

deploymentMode: SimpleScalable

backend:
  replicas: 3
read:
  replicas: 3
write:
  replicas: 3

# Disable minio storage
minio:
  enabled: false

Expected behavior
All pods should be running.

Environment:

  • Infrastructure: AKS
  • Deployment tool: helm

I have pre-created chunks, ruler and admin containers in blob storage. I am not able to get it running even with minio.enabled=true.

@JStickler JStickler added area/helm type/bug Somehing is not working as expected labels Dec 2, 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

2 participants