Telemetry mixer logs

9/11/2019

I deploy istio 1.2.5 on a K8s cluster.

According to documentation https://istio.io/faq/mixer/ in rules section:

kubectl get rules --all-namespaces

You will get the list. In my cluster I got No resources found

But if I use:

kubectl get rules.config.istio.io -n istio-system

I got the list:

NAME                      AGE
kubeattrgenrulerule       5h
promhttp                  5h
promtcp                   5h
promtcpconnectionclosed   5h
promtcpconnectionopen     5h
stdio                     5h
stdiotcp                  5h

Someone know the difference?

Also if I try:

kubectl -n istio-system logs -f istio-telemetry-7df96d454b-4kxs9 -c mixer

I didn't got the log of request in the log ( I found it work in another cluster). Do you know why?

-- erang
istio
kubernetes

1 Answer

9/18/2019

I tried to reproduce your issue on both versions Istio 1.2.5 and Istio 1.3.0 and environments like GKE, Minikube and Kubeadm. I have tried to install it manually and using HELM. Each time everything worked as should.

Based on the information you have provided: I found it work in another cluster and you are using bare metal I would guess that this cluster have some specific configuration or some of the kubernetes/Istio objects have Insufficient resources.

$ kubectl describe node [node-name]

Please keep in mind that you might install Istio Configuration Profile which requested too many resources. Each profile contain different amount of resources based on each object (citadel, egress, galley, pilot, telemetry, etc). For example if you will check Istio Docs

  • The Envoy proxy uses 0.6 vCPU and 50 MB memory per 1000 requests per second going through the proxy.
  • The istio-telemetry service uses 0.6 vCPU per 1000 mesh-wide requests per second.
  • Pilot uses 1 vCPU and 1.5 GB of memory.
-- PjoterS
Source: StackOverflow