Thore Cimbal
6cd6ee618e
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.
40 lines
1.1 KiB
YAML
40 lines
1.1 KiB
YAML
apiVersion: helm.toolkit.fluxcd.io/v2
|
|
kind: HelmRelease
|
|
metadata:
|
|
name: alloy
|
|
namespace: monitoring
|
|
spec:
|
|
interval: 1h
|
|
chart:
|
|
spec:
|
|
chart: alloy
|
|
# ⚠️ Bis 2026-08-21 stand hier "0.x". Das sah nach "bleibt aktuell" aus
|
|
# und war eine DECKE: 0.12.6 ist die letzte 0er-Fassung des Charts, seither
|
|
# erschienen 1.x-Fassungen, die der Bereich nie erreichen konnte. Alloy blieb
|
|
# dadurch auf v1.7.5 stehen (2 CRITICAL) waehrend v1.16.3 keine traegt.
|
|
# Jetzt fest wie jeder andere Release in diesem Repo - eine feste Nummer ist
|
|
# sichtbar veraltet, ein gedeckelter Bereich nicht.
|
|
version: "1.9.0"
|
|
sourceRef:
|
|
kind: HelmRepository
|
|
name: grafana
|
|
namespace: flux-system
|
|
values:
|
|
alloy:
|
|
configMap:
|
|
name: alloy-config
|
|
replicaCount: 1
|
|
serviceAccount:
|
|
create: true
|
|
name: alloy
|
|
rbac:
|
|
create: true
|
|
podAnnotations:
|
|
prometheus.io/scrape: "false"
|
|
resources:
|
|
limits:
|
|
memory: 512Mi
|
|
requests:
|
|
cpu: 100m
|
|
memory: 256Mi
|