How do I configure image registry for loki-logs daemonset?

Grafana Loki
1

Question: How do I configure image registry for loki-logs daemonset?
By setting global.image.registry I have managed to change registry from quay.io to our local registry for everything but the loki-logs daemonset, where I get an ImagePullBackOff.

describe pod...:
.
.
.
Warning  Failed     33m                    kubelet            Failed to pull image "quay.io/prometheus-operator/prometheus-config-reloader:v0.62.0": rpc error: code = Unknown desc = failed to pull and unpack image "quay.io/prometheus-operator/prometheus-config-reloader:v0.62.0": failed to resolve reference "quay.io/prometheus-operator/prometheus-config-reloader:v0.62.0": failed to do request: Head "https://quay.io/v2/prometheus-operator/prometheus-config-reloader/manifests/v0.62.0": read tcp 10.54.14.5:46776->34.228.154.221:443: read: connection reset by peer
  Normal   BackOff    3m34s (x151 over 33m)  kubelet            Back-off pulling image "quay.io/prometheus-operator/prometheus-config-reloader:v0.62.0"

Other pods are running fine, having images in local registry:

describe pod...:
.
.
.
Controlled By:  ReplicaSet/loki-read-5fffc6f6c
Containers:
  loki:
    Container ID:  containerd://7e77e8116503e68e1918eb4039a0bb16ef753d19f9d73c795c6cb1041417efbc
    Image:         crdataikutest.azurecr.io/grafana/loki:2.9.1
    Image ID:      crdataikutest.azurecr.io/grafana/loki@sha256:10e1be117325678a2d3b32a87fed4fc59ed8c3d3eafeccc463f1b6c9b4a1e875
    Ports:         3100/TCP, 9095/TCP, 7946/TCP
1 Like
2

We are dealing with the same problem in our air-gapped installation, any advice from Grafana devs?

3

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.