Skip to content
Documentation
Decisions
0040 · Vendor kubernetes-event-exporter manifests

Vendor kubernetes-event-exporter as plain manifests instead of a Helm chart

Status: Accepted Date: 2026-09-21 Deciders: Smana (Platform Owner)

Context

Issue #1089 tracks migrating every Bitnami-sourced dependency off oci://registry-1.docker.io/bitnamicharts, ahead of Broadcom’s bitnamilegacy deprecation. kubernetes-event-exporter was the last one: the container image already runs ghcr.io/civitatis/kubernetes-event-exporter:1.8 (a community fork), with global.security.allowInsecureImages: true set so the Bitnami chart accepts a non-Bitnami image. Only the chart itself — kubernetes-event-exporter v3.6.3, sourced from the bitnami HelmRepository — was still Bitnami’s.

No comment on #1089 names a mandated replacement chart. Two independent Helm charts exist on ArtifactHub. itakurah’s was rendered with this repo’s values (helm template) and diffed against the Bitnami baseline; ownkube’s is a full rewrite of a different codebase, so it was judged on its source and maintenance record instead — a helm template diff can’t show whether a reimplemented loki receiver behaves the same as the one already running.

Decision

Vendor the Bitnami chart’s own rendered output as plain manifests under observability/base/kubernetes-event-exporter/ (Deployment, ConfigMap, Service, ServiceMonitor, NetworkPolicy, PodDisruptionBudget, RBAC), stripped of Helm-only metadata, and delete the bitnami HelmRepository under flux/sources/. ${cluster_name} stays in the ConfigMap for Flux postBuild substitution, unchanged from how the HelmRelease fed it.

Alternatives rejected

OptionRejected because
itakurah/kubernetes-event-exporter chart (0.2.3)Wraps the same upstream binary this repo already runs, but ships no resources field anywhere in values or templates — violates this repo’s requests+limits non-negotiable and would need a postRenderers JSON6902 patch to add them. Also carries an open, unfixed template bug (an all-hex 8-char config checksum can parse as a YAML number and reject the apply), unpatched for 6+ months.
ownkube/kubernetes-events-exporter chart (0.1.2)A full Go rewrite, not the resmoio/mustafaakin codebase this repo runs — loki receiver and route.match compatibility is unverified, not just untested. Its apparent activity doesn’t hold up either: no human-merged commit in 5 months, only 11 open Dependabot PRs.
Keep pulling the Bitnami OCI chartExactly what #1089 asks to stop. It would also be the last Bitnami dependency left in the repo: Valkey moved off bitnamilegacy in SPEC-012 (2026-07-21), and RabbitMQ’s only use was grafana-oncall, removed outright when ADR-0029 chose RunLore instead.
Use the real upstream chartDoesn’t exist. The upstream repo (resmoio, now pushed under mustafaakin/kubernetes-event-exporter) ships a raw deploy/ manifest directory, not a Helm chart.

Consequences

  • No chart to upgrade. A future exporter version means re-rendering and re-diffing by hand, not bumping a chart version.
  • Config changes are hand edits. config.yaml (routes, receivers, log settings) is now a committed file, edited directly instead of through values.yaml. Kustomize’s configMapGenerator still rolls the pod on a change (see kustomization.yaml), so this only removes the values layer, not the rollout behaviour.
  • The image tag is Renovate-tracked for the first time. The HelmRelease’s split image.registry/image.repository/image.tag values were read by no Renovate manager; the plain image: reference in the vendored Deployment is picked up by the repo-wide kubernetes manager (.github/renovate.json), which already scans every manifest outside clusters/ and opentofu/.
0039 · go-task as the entry pointTemplate