#Istio is not easy to debug. But this time I found a problem which is really simple to reproduce and easy to observe via #Prometheus
```
sum(changes(kube_pod_container_status_ready{container="istio-proxy"}[1m]))
```
https://github.com/istio/istio/issues/56257

But then, why am I not seeing more people reporting this problem? 🤔

#kubernetes #k8s #cloud #cloudComputing #grafana

some #Linux sysadmins aren't looking for anything logical, like stability or user-friendliness. They can't be bought with pretty GUIs, bullied by error messages, reasoned with by support forums, or negotiated with by desperate end-users.

Some sysadmins just want to watch the world burn...

...as they compile their own Linux kernel with the most experimental flags.
...as they change root permissions on a live production server
...as they replace core system libraries with unstable nightly builds

China: “Remove all VPNs”
Apple: “Sure thing”

China: “…and podcast apps”
Apple: “Can do boss!”

China: “…and also hand over all iCloud data for our citizens”
Apple: “I mean why wouldn’t we? Here you go!”

EU: “Allow alternate app stores, and do it fairly”
Apple: “Ahhh hell no! This is so unfair you guys are bullies! Malware! Privacy! We have standards! Unlike you we care about our users!”

We have an AWS Elastic Kubernetes Service cluster with Karpenter which is responsible for EC2 auto-scaling, see AWS: Getting started with Karpenter for autoscaling in EKS, and its installation with Helm.
In general, there are no problems with it so far, but in any case we need to monitor it. For its monitoring, Karpenter provides metrics out of […]

https://rtfm.co.ua/en/karpenter-its-monitoring-and-grafana-dashboard-for-kubernetes-workernodes/