You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
error: (status=400): {"type":"mapper_parsing_exception","reason":"object mapping for [kubernetes.labels.role] tried to parse field [role] as object, but found a concrete value"}
why this issue occurred:
for k8s component
quay.io/calico/node:v2.6.7
quay.io/calico/cni:v1.11.2
quay.io/calico/kube-controllers:v1.0.3
Hi @kuzm1ch, thanks for taking the time of reporting this issue. I think it is the same problem as in #8773. I am going to close this one so we keep all discussions in the same thread.
Similar to
https://github.com/elastic/beats/issues/8773
but related to metricbeat.metricbeat: 6.4.2
kubernetes: v1.10.6
kube-state-metrics: k8s.gcr.io/addon-resizer:1.8.3
error:
(status=400): {"type":"mapper_parsing_exception","reason":"object mapping for [kubernetes.labels.role] tried to parse field [role] as object, but found a concrete value"}
why this issue occurred:
for k8s component
quay.io/calico/node:v2.6.7
quay.io/calico/cni:v1.11.2
quay.io/calico/kube-controllers:v1.0.3
should be parse as kubernetes.labels : role.kubernetes.io/networking=1
because what we have an k8s calico default pod
kubectl describe pods ...
The same issue exist for ingress-nginx
kubernetes.labels.app
:The text was updated successfully, but these errors were encountered: