MikeHsu0618/grafana-stack-in-kubernetes

What linux Distribution you use in day31?

Closed this issue · 1 comments

I follow this link https://ithelp.ithome.com.tw/articles/10340539
in my case in centos7 and linux kernel 6.6.8.1-1.el7.elrepo.x86_64 with k3s 1.28

all pod are running, but when access grafana have no trace data, cloud you help me email(Wechat): 553069938

[root@VM-16-2-centos ~]# kubectl get pod -A
NAMESPACE       NAME                                                   READY   STATUS      RESTARTS      AGE
kube-system     helm-delete-traefik-r4ksc                              0/1     Completed   0             13d
ingress-nginx   ingress-nginx-admission-create-k4hjk                   0/1     Completed   0             13d
ingress-nginx   ingress-nginx-admission-patch-6wqqq                    0/1     Completed   1             13d
kube-system     helm-install-traefik-crd-pvsmq                         0/1     Completed   0             18h
kube-system     helm-install-traefik-7rwfp                             0/1     Completed   1             18h
prometheus      prometheus-stack-admission-patch-qr9hj                 0/1     Completed   0             17h
odigos-system   odigos-autoscaler-6c959dfb66-n5ztx                     1/1     Running     2 (16h ago)   18h
default         jxmysql-0                                              1/1     Running     2 (16h ago)   18h
odigos-system   odigos-instrumentor-bc49b5d57-j7wxf                    1/1     Running     3 (16h ago)   18h
odigos-system   odigos-scheduler-7b6d985f8d-cq4r7                      1/1     Running     3 (16h ago)   18h
odigos-system   odigos-gateway-5c8f885567-ckhpn                        1/1     Running     2 (16h ago)   16h
odigos-system   odigos-data-collection-l7p6v                           1/1     Running     2 (16h ago)   16h
kube-system     coredns-6799fbcd5-l55cv                                1/1     Running     3 (16h ago)   13d
odigos-system   odiglet-j5sfb                                          1/1     Running     4 (15h ago)   18h
kube-system     local-path-provisioner-84db5d44d9-prz4c                1/1     Running     6 (15h ago)   13d
ingress-nginx   ingress-nginx-controller-ltnq4                         1/1     Running     3 (16h ago)   13d
kube-system     metrics-server-67c658944b-5n7s2                        1/1     Running     6 (15h ago)   13d
tracing         tempo-compactor-588ff6c55c-6rncp                       1/1     Running     0             15h
tracing         tempo-query-frontend-7569cffb65-9w7t5                  1/1     Running     0             15h
tracing         tempo-memcached-0                                      2/2     Running     0             15h
default         jxsy-7fd7594b6-nssr5                                   1/1     Running     0             15h
tracing         tempo-gateway-999cd48f5-tt9rc                          1/1     Running     0             15h
tracing         tempo-querier-7ff8c97c7c-q5cz4                         1/1     Running     0             15h
tracing         tempo-distributor-86f8679594-jkrp2                     1/1     Running     0             15h
tracing         tempo-metrics-generator-65745665d4-nfqkc               1/1     Running     0             15h
tracing         tempo-ingester-0                                       1/1     Running     0             15h
tracing         tempo-ingester-2                                       1/1     Running     0             15h
tracing         tempo-ingester-1                                       1/1     Running     0             15h
prometheus      prometheus-stack-kube-state-metrics-6d555c6cb9-xkwrg   1/1     Running     0             15h
prometheus      prometheus-stack-grafana-8486bbd666-6gz24              3/3     Running     0             15h

Hi @laoyang103,

I'm unable to precisely answer your question due to the variability in environments.

The requirements for using eBPF may necessitate checking your Linux kernel version and your CNI among other factors. Different kernel versions might have varying levels of support for eBPF features, and the CNI plugin directly affects the implementation of networking functionalities for containers.