helm_lib_prometheus_rules only renders when "operator-prometheus-crd" is an enabled module; on DKP 1.76 that module doesn't exist (the CRDs come with operator-prometheus), so the two alerts were silently dropped on a live install. Gate on the PrometheusRule API instead. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
16 lines
818 B
YAML
16 lines
818 B
YAML
v0.7.1:
|
|
fixes:
|
|
- Alert rules are rendered on DKP versions without the operator-prometheus-crd module.
|
|
v0.7.0:
|
|
features:
|
|
- First release as a Deckhouse module (ModuleSource, release channels, lib-helm templates).
|
|
- "Traffic collection modes: Continuous, OnDemand, Disabled; retention configurable up to 24h."
|
|
- Hubble CA is read by a module hook from d8-cni-cilium; no manual copy of the certificate.
|
|
- Authentication through user-authn (DexAuthenticator) or any external auth, as in cilium-hubble.
|
|
- English and Russian UI.
|
|
- Prometheus metrics and alerts for the Hubble stream.
|
|
fixes:
|
|
- Traffic windows now cover the requested time instead of the agent ring buffer (about 10 seconds).
|
|
- Counts are distinct connections, not Hubble events.
|
|
- Pod exits cleanly on SIGTERM.
|