Files
axion1337.chat-gitops/apps
Thore Cimbal 6cd6ee618e monitoring: the two charts on a floating range were the two left behind
Every other release in this repo pins an exact version. Exactly two used a
range, and exactly those two stopped receiving updates: 0.12.6 is the last 0.x
alloy chart and 5.37.0 the last 5.x kube-state-metrics, so both ranges had been
sitting on a ceiling that reads as 'stays current'. A pinned version at least
looks stale.

Rendered both versions of each chart against our real values before changing
anything, because a chart jump moved an internal endpoint out from under a
network rule earlier today. Same objects, same selectors, same service names;
kube-state-metrics names its targetPort instead of numbering it and swaps
endpoints for endpointslices, neither of which our policies or scrapes touch.

nginx for the docs server goes along: 1.26-alpine carried two criticals,
1.31.4-alpine measures clean.
2026-08-21 12:00:00 +00:00
..