guys,
I used helm tool to install otel-demo in my k8s cluster, run the following command:
helm install my-otel-demo open-telemetry/opentelemetry-demo
And I waited for some minutes, use the command
kubectl get pod
And I found that:
NAME READY STATUS RESTARTS AGE
my-otel-demo-accountingservice-576d957954-wmcmw 1/1 Running 0 37m
my-otel-demo-adservice-fc5b87d6c-9jwr6 1/1 Running 0 37m
my-otel-demo-cartservice-5887676bc6-qz6bj 1/1 Running 0 37m
my-otel-demo-checkoutservice-566b544fc5-vnvp6 1/1 Running 0 37m
my-otel-demo-currencyservice-7f6974d6f-kjjmf 1/1 Running 0 37m
my-otel-demo-emailservice-645d9f4b7b-wkm94 1/1 Running 0 37m
my-otel-demo-flagd-5bc8d949d6-b29zr 2/2 Running 0 37m
my-otel-demo-frauddetectionservice-955684b8d-wrl98 1/1 Running 0 37m
my-otel-demo-frontend-5cff554bd6-hl5rm 1/1 Running 0 37m
my-otel-demo-frontendproxy-9874cb858-kgj72 1/1 Running 0 37m
my-otel-demo-grafana-d7476ff94-mgvtl 0/1 CrashLoopBackOff 10 (4m47s ago) 37m
my-otel-demo-imageprovider-59648dc969-jq8tb 1/1 Running 0 37m
my-otel-demo-jaeger-694b669cc8-kbt6j 1/1 Running 0 37m
my-otel-demo-kafka-589d5c4dcd-tnqzl 1/1 Running 0 37m
my-otel-demo-loadgenerator-6b7fddb4d9-gs6t6 1/1 Running 0 37m
my-otel-demo-otelcol-548877cf-2sh4x 1/1 Running 0 37m
my-otel-demo-paymentservice-dcf745bc6-sqz2z 1/1 Running 0 37m
my-otel-demo-productcatalogservice-5fdf7b87d6-7m6rn 1/1 Running 0 37m
my-otel-demo-prometheus-server-56fb7845b9-qtnw5 1/1 Running 0 37m
my-otel-demo-quoteservice-d7c966699-7k5rg 1/1 Running 0 37m
my-otel-demo-recommendationservice-59448d97f9-zs7mc 1/1 Running 0 37m
my-otel-demo-shippingservice-74b4cd9ff8-xqsrb 1/1 Running 0 37m
my-otel-demo-valkey-558b4588d8-wp7gs 1/1 Running 0 37m
otel-demo-opensearch-0 1/1 Running 0 37m
And I used kubectl logs my-otel-demo-grafana-d7476ff94-mgvtl
and found :
Error: ✗ Get "https://grafana.com/api/plugins/grafana-opensearch-datasource/versions": dial tcp: lookup grafana.com on 10.96.0.10:53: server misbehaving
and
# kubectl describe pod my-otel-demo-grafana-d7476ff94-mgvtl
...
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 45m default-scheduler Successfully assigned default/my-otel-demo-grafana-d7476ff94-mgvtl to node-1
Normal Pulling 45m kubelet Pulling image "docker.io/grafana/grafana:11.3.1"
Normal Pulled 40m kubelet Successfully pulled image "docker.io/grafana/grafana:11.3.1" in 5m7.830781113s
Normal Started 39m (x3 over 39m) kubelet Started container grafana
Warning Unhealthy 39m (x9 over 39m) kubelet Readiness probe failed: Get "http://10.0.0.188:3000/api/health": dial tcp 10.0.0.188:3000: connect: connection refused
Normal Created 38m (x4 over 39m) kubelet Created container grafana
Normal Pulled 38m (x3 over 39m) kubelet Container image "docker.io/grafana/grafana:11.3.1" already present on machine
Warning BackOff 4m59s (x159 over 39m) kubelet Back-off restarting failed container
My cluster coreDNS
pod is running. I do not know how to fix the problem. Thank you for your help!
I want to see the effect of OpenTelemetry, then install it for the microservices on my cluster, and finally do some telemery work.
we1ru1 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.