From f74870b2466dc5c43f37a9778be6df00c504d207 Mon Sep 17 00:00:00 2001 From: jklein Date: Sun, 23 Aug 2026 20:46:50 +0200 Subject: [PATCH] apache-tika: note why the notes use effectiveResources Records the reasoning inline, matching the comment the gotenberg chart carries, so the next edit does not quietly switch back to the raw helper and drop the paragraph whenever a resources: block has been erased. --- apache-tika/templates/NOTES.txt | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/apache-tika/templates/NOTES.txt b/apache-tika/templates/NOTES.txt index 5867f4e..f898ddf 100644 --- a/apache-tika/templates/NOTES.txt +++ b/apache-tika/templates/NOTES.txt @@ -1,4 +1,8 @@ {{- $replicas := include "apache-tika.replicas" (dict "scaleDown" .Values.scaleDown "replicas" .Values.tika.replicas) -}} +{{- /* effectiveResources, not resources: an erased "resources:" block falls back + to the chart defaults in the Deployment (#99), so the notes must report the + limits the release actually gets — and the heap figure below is derived from + that same effective limit, not from the raw value. */ -}} {{- $limits := (include "apache-tika.effectiveResources" .Values.tika.resources | fromYaml).limits | default dict -}} {{- $memLimit := index $limits "memory" -}} {{- $svc := printf "%s-%s-service" .Release.Name .Chart.Name -}}