Uploaded image for project: 'OpenShift Logging'
  1. OpenShift Logging
  2. LOG-2278

[loki-operator] SRV lookup for components fails because of service name mismatch

    XMLWordPrintable

Details

    • False
    • False
    • NEW
    • OBSDA-7 - Adopting Loki as an alternative to Elasticsearch to support more lightweight, easier to manage/operate storage scenarios
    • VERIFIED
    • Logging (LogExp) - Sprint 215

    Description

      When running Loki components deployed using loki-operator some of them are currently reporting an error like this every few seconds:

      level=info ts=2022-02-24T16:29:56.763760598Z caller=dns_resolver.go:209 msg="failed DNS SRV record lookup" err="lookup _grpclb._tcp.loki-query-frontend-grpc-lokistack-dev.default.svc.cluster.local on 10.96.0.10:53: no such host"

      This is because the SRV lookup is looking for a "grpclb" service but our Kubernetes Services define a "grpc" service instead (see here).

      From what I can see the lookup uses the A record available on the k8s Service DNS address as a fallback.

      Attachments

        Issue Links

          Activity

            People

              rojacob@redhat.com Robert Jacob
              rojacob@redhat.com Robert Jacob
              Kabir Bharti Kabir Bharti
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: