Hacker News Reader

configmap that was updated recently and incorrectly: how would you know the cm update is the cause? How would you sort that out if you made 5/10 updates?

say a node is low on disk: what about setting up monitoring alerts for those king of things.

In general, alerts are of great help. An alert fired after an update is a big smell about that update causing the issue.

View on HN

So if there is a spike on say errors, you do a group by pod, click on the pod in the legend, see the k8s neighborhood which means discover the pod --> config map association. You see the config map and all the recent updates to it, and can even diff them like code.

An alert on the other hand, say on a node that is low on disk, doesn't automatically tell you all the affected workloads. Not saying the alert doesn't help, but this experience helps identify the affected pods and apps much faster.

Reply on news.ycombinator.com