rss-bridge: new chart

Takes over the four loose manifests in cluster-config/rss-bridge/ as a
proper chart, on the current template-chart standard: strict values
schema, null-safe helpers, computed limits, replicas/scaleDown,
checksum/config, NOTES.txt.

Two things deviate from the repo standard on purpose:

- The Ingress models host AND TLS secret name per entry instead of the
  single conventional tls-<release>-<chart>-ingress. The installation
  this replaces has grown three separate certificates, one per host.
  Renaming them would make cert-manager issue three new ones and leave
  each host unreachable until it did - a self-inflicted outage on a
  deployment that has been up for over a year. Entries sharing a secret
  name are grouped into one tls entry, and omitting the name falls back
  to the convention, so consolidating later is a values change.

- Requests and limits are decoupled. The old manifest requested 2Gi of
  ephemeral storage, identical to its limit, reserving two gigabytes for
  a workload measured at 2.2 MB after fetching all five whitelisted
  bridges. The request drops to 64Mi; the limit stays at 2Gi.

Hardening was verified rather than assumed. The image ships no USER and
runs as root by default, but runs fully hardened once its writable paths
are provided: uid/gid 33, readOnlyRootFilesystem, all capabilities
dropped, seccompProfile RuntimeDefault. The writable paths were found by
running the image with a writable rootfs, exercising every bridge and
reading its diff layer - /app/cache, /run, /run/php, /var/lib/nginx.
/tmp did not show up that way, because PHP's opcache creates its lock
file there and unlinks it immediately; it only surfaced when the
hardened container died at startup. Stopping at the first writable path
would have shipped a chart that cannot start.

Probes use the app's own /?action=health, which renders fixed JSON
without touching the cache or any remote site, so neither a scraped site
going down nor an unwritable cache can restart the pod.

Fixes #128

rss-bridge/templates/NOTES.txt

@@ -0,0 +1,42 @@
+RSS-Bridge {{ .Chart.AppVersion }} was installed as release "{{ .Release.Name }}".
+
+{{ if .Values.ingress.enabled -}}
+Reachable at:
+{{ range $entry := .Values.ingress.hosts }}  https://{{ $entry.host }}
+{{ end }}
+Each host serves the same instance. Certificates are issued by the
+cert-manager cluster issuer "{{ .Values.ingress.clusterIssuer }}" into these secrets:
+{{ range $secret := (fromYaml (include "rss-bridge.tlsGroups" (dict "hosts" .Values.ingress.hosts "root" $))).order }}  {{ $secret }}
+{{ end }}
+{{- else -}}
+The Ingress is disabled (ingress.enabled=false). Reach the instance with:
+
+  kubectl --namespace {{ .Release.Namespace }} port-forward svc/{{ .Release.Name }}-{{ .Chart.Name }}-service 8080:80
+
+and open http://localhost:8080
+{{- end }}
+
+Enabled bridges ({{ len .Values.whitelist }} entr{{ if eq (len .Values.whitelist) 1 }}y{{ else }}ies{{ end }} in whitelist.txt):
+{{ range $entry := .Values.whitelist }}  {{ $entry }}
+{{ end }}
+{{- if has "*" .Values.whitelist }}
+"*" enables every bridge the image ships. Narrow it down by listing bridge
+names in the "whitelist" value.
+{{- end }}
+
+Useful to know:
+
+  * Health endpoint: /?action=health - a fixed JSON document that touches
+    neither the cache nor any remote site. All three probes use it.
+  * Changing the "whitelist" value rolls the pod: the deployment carries a
+    checksum over the ConfigMap, because a subPath mount would otherwise never
+    reach the running container.
+  * The feed cache lives in an emptyDir at /app/cache and is therefore
+    deliberately lost on every restart. RSS-Bridge refills it on demand; it
+    holds only fetched feeds, no configuration and no user data.
+  * The container runs read-only and non-root as uid 33 (www-data).
+{{- if .Values.scaleDown }}
+
+WARNING: scaleDown is true, so this release is running with 0 replicas.
+Set scaleDown=false to bring it back up.
+{{- end }}

rss-bridge/templates/_helpers.tpl

@@ -0,0 +1,313 @@
+{{/*
+Render the body of a container "resources:" block from a values dict of the form
+
+  resources:
+    limitFactor: 3          # optional, default 3
+    requests: { cpu, memory, ephemeral-storage / ephemeralStorage, ... }
+    limits:   { ... }       # optional, every entry optional
+
+Rules (variant B, see issue #19):
+  - requests are rendered as given (camelCase "ephemeralStorage" is normalized
+    to the Kubernetes key "ephemeral-storage").
+  - an explicitly set limit always wins.
+  - a missing memory / ephemeral-storage limit is computed as
+    limitFactor x the corresponding request.
+  - a missing cpu limit is NOT set at all (the kubelet then treats CPU as
+    unlimited; CPU is compressible, so this cannot kill the workload).
+
+NOTE: charts in this repo deliberately have no dependencies, so this helper is
+duplicated into every chart's templates/_helpers.tpl with the chart's name as
+define prefix. template-chart holds the reference implementation.
+*/}}
+{{- define "rss-bridge.resources" -}}
+{{- $resources := . | default dict -}}
+{{- $factor := 3.0 -}}
+{{- if not (kindIs "invalid" $resources.limitFactor) -}}
+{{- $factor = float64 $resources.limitFactor -}}
+{{- end -}}
+{{- $requests := dict -}}
+{{- range $key, $value := ($resources.requests | default dict) -}}
+{{- if not (kindIs "invalid" $value) -}}
+{{- $_ := set $requests (include "rss-bridge.resourceKey" $key) $value -}}
+{{- end -}}
+{{- end -}}
+{{- $limits := dict -}}
+{{- range $key, $value := ($resources.limits | default dict) -}}
+{{- if not (kindIs "invalid" $value) -}}
+{{- $_ := set $limits (include "rss-bridge.resourceKey" $key) $value -}}
+{{- end -}}
+{{- end -}}
+{{- range $key, $request := $requests -}}
+{{- if and (ne $key "cpu") (not (hasKey $limits $key)) -}}
+{{- $_ := set $limits $key (include "rss-bridge.multiplyQuantity" (dict "quantity" $request "factor" $factor)) -}}
+{{- end -}}
+{{- end -}}
+{{- $out := dict -}}
+{{- with $requests }}{{- $_ := set $out "requests" . }}{{- end -}}
+{{- with $limits }}{{- $_ := set $out "limits" . }}{{- end -}}
+{{- toYaml $out -}}
+{{- end -}}
+
+{{/*
+Normalize a resource name from values to its Kubernetes key.
+*/}}
+{{- define "rss-bridge.resourceKey" -}}
+{{- if eq . "ephemeralStorage" -}}ephemeral-storage{{- else -}}{{ . }}{{- end -}}
+{{- end -}}
+
+{{/*
+Multiply a Kubernetes quantity by a factor, keeping its suffix.
+Input: dict "quantity" <string|number> "factor" <float64>.
+Handles plain numbers ("2", "0.5", 1073741824), decimal ("1.5Gi"), binary
+("512Mi", "1Gi", "10Ki") and milli/SI suffixes ("100m", "500M"). Integer
+results are printed without a decimal point.
+*/}}
+{{- define "rss-bridge.multiplyQuantity" -}}
+{{- $quantity := printf "%v" .quantity -}}
+{{- $number := regexFind "^[0-9]+(\\.[0-9]+)?" $quantity -}}
+{{- if not $number -}}
+{{- fail (printf "cannot parse resource quantity %q" $quantity) -}}
+{{- end -}}
+{{- $suffix := trimPrefix $number $quantity -}}
+{{- if not (regexMatch "^(m|k|M|G|T|P|E|Ki|Mi|Gi|Ti|Pi|Ei)?$" $suffix) -}}
+{{- fail (printf "unsupported resource quantity suffix %q in %q" $suffix $quantity) -}}
+{{- end -}}
+{{- $product := mulf (float64 $number) .factor -}}
+{{- if eq $product (floor $product) -}}
+{{- printf "%d%s" (int64 $product) $suffix -}}
+{{- else -}}
+{{- printf "%v%s" $product $suffix -}}
+{{- end -}}
+{{- end -}}
+
+{{/*
+Render the replica count for a Deployment/StatefulSet.
+
+Input: dict
+  "scaleDown"  the chart-global .Values.scaleDown flag (may be nil)
+  "replicas"   the workload's replicas value (may be nil)
+
+Rules (issue #25):
+  - scaleDown: true takes precedence and always yields 0.
+  - otherwise an explicitly set replicas value is used as given, including an
+    explicit 0 - Helm's "default" would swallow 0, hence the explicit
+    kindIs "invalid" nil check.
+  - a missing replicas value defaults to 1.
+*/}}
+{{- define "rss-bridge.replicas" -}}
+{{- if .scaleDown -}}
+0
+{{- else if not (kindIs "invalid" .replicas) -}}
+{{- .replicas -}}
+{{- else -}}
+1
+{{- end -}}
+{{- end -}}
+
+{{/*
+Merge a user-supplied values sub-tree onto a dict of chart defaults so that a
+null / empty override falls back to the defaults instead of erasing them.
+
+Input: dict "defaults" <dict> "given" <dict|nil> "path" <string, optional
+values path used in error messages>. Output: YAML of the merged dict (consume
+it with fromYaml).
+
+Why this exists (issues #61 and #99): Helm merges values maps recursively, but
+an override key written without children - e.g. a leftover
+
+  securityContext:
+
+after deleting its last remaining sub-key - is YAML null. Where the chart
+defines a default, Helm treats that null as a deletion of the default; the
+template then renders "securityContext: null": no readOnlyRootFilesystem, no
+dropped capabilities, no allowPrivilegeEscalation: false. The workload starts
+and reports healthy while being unhardened, so nothing points at the mistake.
+The same shape erases a probe (it disappears) or the resources block (no
+requests, no computed limits). This helper defines the opposite semantics: an
+empty block means "chart defaults apply".
+
+Rules:
+  - a nil "given" is treated as an empty dict (all defaults apply).
+  - a key whose override value is null keeps the default (nulls never delete).
+  - a key present in both as a map is merged recursively, so a partially
+    filled block only overrides the keys it actually sets.
+  - a scalar override for a key the defaults define as a map is rejected with
+    a message naming the values path, instead of failing later with a template
+    field error.
+  - any other set value wins as given, including an explicit false or 0 -
+    Helm's "default" and sprig's "mergeOverwrite" would both swallow those
+    zero values, hence the explicit kindIs "invalid" nil check.
+  - keys only present in the override are passed through unchanged.
+*/}}
+{{- define "rss-bridge.defaultedDict" -}}
+{{- $defaults := .defaults | default dict -}}
+{{- $given := .given -}}
+{{- $path := .path | default "value" -}}
+{{- if kindIs "invalid" $given -}}
+{{- $given = dict -}}
+{{- end -}}
+{{- if not (kindIs "map" $given) -}}
+{{- fail (printf "%s must be a mapping or null, got %s (%v)" $path (kindOf $given) $given) -}}
+{{- end -}}
+{{- $out := deepCopy $defaults -}}
+{{- range $key, $value := $given -}}
+{{- if not (kindIs "invalid" $value) -}}
+{{- $default := index $defaults $key -}}
+{{- if and (kindIs "map" $value) (kindIs "map" $default) -}}
+{{- $_ := set $out $key (fromYaml (include "rss-bridge.defaultedDict" (dict "defaults" $default "given" $value "path" (printf "%s.%s" $path $key)))) -}}
+{{- else if kindIs "map" $default -}}
+{{- fail (printf "%s.%s must be a mapping or null, got %s (%v)" $path $key (kindOf $value) $value) -}}
+{{- else -}}
+{{- $_ := set $out $key $value -}}
+{{- end -}}
+{{- end -}}
+{{- end -}}
+{{- toYaml $out -}}
+{{- end -}}
+
+{{/*
+Pick one sub-block out of a values block that may itself be null.
+
+Input: dict "block" <dict|nil> "key" <string> "path" <string>.
+Returns YAML of dict "value" <the sub-block, may be nil>, after rejecting a
+non-mapping block with a message that names the values path. Needed because
+".Values.rssBridge.securityContext" can itself be erased, and indexing into nil
+inside a template is not an error but silently yields nothing.
+*/}}
+{{- define "rss-bridge.subBlock" -}}
+{{- $block := .block -}}
+{{- if kindIs "invalid" $block -}}
+{{- $block = dict -}}
+{{- end -}}
+{{- if not (kindIs "map" $block) -}}
+{{- fail (printf "%s must be a mapping or null, got %s (%v)" .path (kindOf $block) $block) -}}
+{{- end -}}
+{{- toYaml (dict "value" (index $block .key)) -}}
+{{- end -}}
+
+{{/*
+The effective security contexts, probes and resources (issue #99).
+
+The defaults below MUST stay in sync with the corresponding blocks in
+values.yaml, which stays the documented, user-facing place for them; this copy
+is only the fallback for the case where an override has erased the block.
+
+Two chart-specific facts a rebuilt default must not lose:
+
+  - uid/gid 33 (www-data) is not a stylistic choice. The image ships /app and
+    everything in it owned by www-data, and both nginx and php-fpm are
+    configured for that user. A "cleaner" high uid would leave the app unable
+    to read its own bridge sources.
+  - the probes address the port BY NAME (rss-bridge-port) and use the app's
+    own health action. A default that drops the query string would probe the
+    1.5 MB front page instead of a 49-byte JSON response, and a default that
+    drops the port name would not resolve at all.
+*/}}
+{{- define "rss-bridge.podSecurityContext" -}}
+{{- $given := (fromYaml (include "rss-bridge.subBlock" (dict "block" . "key" "pod" "path" "rssBridge.securityContext"))).value -}}
+{{- $defaults := dict
+      "runAsNonRoot" true
+      "runAsUser" 33
+      "runAsGroup" 33
+      "fsGroup" 33
+      "fsGroupChangePolicy" "Always"
+      "seccompProfile" (dict "type" "RuntimeDefault") -}}
+{{- include "rss-bridge.defaultedDict" (dict "defaults" $defaults "given" $given "path" "rssBridge.securityContext.pod") -}}
+{{- end -}}
+
+{{- define "rss-bridge.containerSecurityContext" -}}
+{{- $given := (fromYaml (include "rss-bridge.subBlock" (dict "block" . "key" "container" "path" "rssBridge.securityContext"))).value -}}
+{{- $defaults := dict
+      "allowPrivilegeEscalation" false
+      "readOnlyRootFilesystem" true
+      "runAsNonRoot" true
+      "capabilities" (dict "drop" (list "ALL")) -}}
+{{- include "rss-bridge.defaultedDict" (dict "defaults" $defaults "given" $given "path" "rssBridge.securityContext.container") -}}
+{{- end -}}
+
+{{/*
+The probe target, shared by all three probes.
+
+"/?action=health" is RSS-Bridge's own health action: it renders a fixed JSON
+document and touches neither the file cache nor any remote site, so no outage
+of a scraped website and no unwritable cache directory can restart the pod
+(guideline 3). The front page "/" would be a bad choice for the opposite
+reason - it enumerates every bridge and answers with ~1.5 MB.
+*/}}
+{{- define "rss-bridge.probeHttpGet" -}}
+{{- dict "path" "/?action=health" "port" "rss-bridge-port" | toYaml -}}
+{{- end -}}
+
+{{- define "rss-bridge.livenessProbe" -}}
+{{- $defaults := dict
+      "httpGet" (fromYaml (include "rss-bridge.probeHttpGet" .))
+      "periodSeconds" 10
+      "timeoutSeconds" 5
+      "failureThreshold" 3 -}}
+{{- include "rss-bridge.defaultedDict" (dict "defaults" $defaults "given" . "path" "rssBridge.livenessProbe") -}}
+{{- end -}}
+
+{{- define "rss-bridge.readinessProbe" -}}
+{{- $defaults := dict
+      "httpGet" (fromYaml (include "rss-bridge.probeHttpGet" .))
+      "periodSeconds" 10
+      "timeoutSeconds" 5
+      "failureThreshold" 3 -}}
+{{- include "rss-bridge.defaultedDict" (dict "defaults" $defaults "given" . "path" "rssBridge.readinessProbe") -}}
+{{- end -}}
+
+{{- define "rss-bridge.startupProbe" -}}
+{{- $defaults := dict
+      "httpGet" (fromYaml (include "rss-bridge.probeHttpGet" .))
+      "periodSeconds" 5
+      "timeoutSeconds" 5
+      "failureThreshold" 30 -}}
+{{- include "rss-bridge.defaultedDict" (dict "defaults" $defaults "given" . "path" "rssBridge.startupProbe") -}}
+{{- end -}}
+
+{{/*
+The effective resources block, fed into the resources helper above so that an
+erased "resources:" still yields the chart's requests and computed limits
+instead of a container without any resource accounting.
+
+The explicit limits are part of the default on purpose - see the measurements
+in values.yaml. Reproducing only the requests here would let limitFactor
+compute a 384Mi memory limit, which is below the measured concurrent peak.
+*/}}
+{{- define "rss-bridge.effectiveResources" -}}
+{{- $defaults := dict
+      "limitFactor" 3
+      "requests" (dict "cpu" 0.1 "memory" "128Mi" "ephemeral-storage" "64Mi")
+      "limits" (dict "memory" "512Mi" "ephemeral-storage" "2Gi") -}}
+{{- $merged := fromYaml (include "rss-bridge.defaultedDict" (dict "defaults" $defaults "given" . "path" "rssBridge.resources")) -}}
+{{- include "rss-bridge.resources" $merged -}}
+{{- end -}}
+
+{{/*
+Group the configured ingress hosts by their TLS secret name.
+
+Returns YAML of dict "order" <list of secret names, in first-appearance order>
+and "groups" <secret name -> list of hosts>. Hosts that share a secret name end
+up in one tls entry (one certificate with several SANs); hosts with distinct
+names keep one certificate each, which is what the existing installation needs
+(see the TLS comment in values.yaml).
+
+First-appearance order rather than sorted order, so the rendered tls list can
+be compared line by line against the manifest the chart replaces.
+*/}}
+{{- define "rss-bridge.tlsGroups" -}}
+{{- $root := .root -}}
+{{- $default := printf "tls-%s-%s-ingress" $root.Release.Name $root.Chart.Name -}}
+{{- $groups := dict -}}
+{{- $order := list -}}
+{{- range $entry := .hosts -}}
+{{- $host := required "Every ingress.hosts entry needs a host (ingress.hosts[].host)" $entry.host -}}
+{{- $secret := $entry.tlsSecretName | default $default -}}
+{{- if not (hasKey $groups $secret) -}}
+{{- $_ := set $groups $secret (list) -}}
+{{- $order = append $order $secret -}}
+{{- end -}}
+{{- $_ := set $groups $secret (append (index $groups $secret) $host) -}}
+{{- end -}}
+{{- toYaml (dict "order" $order "groups" $groups) -}}
+{{- end -}}

rss-bridge/templates/rss-bridge.configmap.yaml

@@ -0,0 +1,11 @@
+apiVersion: v1
+kind: ConfigMap
+metadata:
+  name: "{{ .Release.Name }}-{{ .Chart.Name }}-configmap"
+data:
+  # One bridge name per line. The application trims every line and drops empty
+  # ones, so the block scalar style is not load-bearing.
+  whitelist.txt: |-
+    {{- range $entry := required "A bridge whitelist must be provided (whitelist)" .Values.whitelist }}
+    {{ $entry }}
+    {{- end }}

rss-bridge/templates/rss-bridge.deployment.yaml

@@ -0,0 +1,130 @@
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: {{ .Release.Name }}-{{ .Chart.Name }}-deployment
+  labels:
+    app: {{ .Release.Name }}-{{ .Chart.Name }}-deployment
+spec:
+  replicas: {{ include "rss-bridge.replicas" (dict "scaleDown" .Values.scaleDown "replicas" .Values.rssBridge.replicas) }}
+  selector:
+    matchLabels:
+      app: {{ .Release.Name }}-{{ .Chart.Name }}-deployment
+  template:
+    metadata:
+      name: {{ .Release.Name }}-{{ .Chart.Name }}-deployment
+      labels:
+        app: {{ .Release.Name }}-{{ .Chart.Name }}-deployment
+      annotations:
+        # Hash of the rendered ConfigMap: a changed whitelist changes the pod
+        # template and thus rolls the pods. Without it a config change stays
+        # invisible to the running container - whitelist.txt is a subPath
+        # mount, which the kubelet never updates, and RSS-Bridge reads the file
+        # once at request bootstrap from the path it was started with.
+        checksum/config: {{ include (print $.Template.BasePath "/rss-bridge.configmap.yaml") . | sha256sum }}
+    spec:
+      automountServiceAccountToken: false
+      securityContext:
+        {{- include "rss-bridge.podSecurityContext" .Values.rssBridge.securityContext | nindent 8 }}
+      containers:
+        - name: {{ .Release.Name }}-{{ .Chart.Name }}-deployment
+          image: "rssbridge/rss-bridge:{{ .Chart.AppVersion }}"
+          imagePullPolicy: IfNotPresent
+          env:
+            {{- range $value := .Values.rssBridge.env }}
+            {{- if $value.value }}
+            - name: {{ $value.name }}
+              value: {{ tpl $value.value $ }}
+            {{- else if $value.valueFrom }}
+            {{- if $value.valueFrom.secretKeyRef }}
+            - name: {{ $value.name }}
+              valueFrom:
+                secretKeyRef:
+                  name: {{ tpl $value.valueFrom.secretKeyRef.name $ }}
+                  key: {{ tpl $value.valueFrom.secretKeyRef.key $ }}
+            {{- else if $value.valueFrom.configMapKeyRef }}
+            - name: {{ $value.name }}
+              valueFrom:
+                configMapKeyRef:
+                  name: {{ tpl $value.valueFrom.configMapKeyRef.name $ }}
+                  key: {{ tpl $value.valueFrom.configMapKeyRef.key $ }}
+            {{- end }}
+            {{- end }}
+            {{- end }}
+          ports:
+            # The port NAME is load-bearing and must not be renamed: the
+            # Service selects it by name (targetPort: rss-bridge-port), and so
+            # do the probes.
+            - containerPort: 80
+              protocol: TCP
+              name: rss-bridge-port
+          # Probes, resources and both security contexts go through the
+          # null-safe helpers (#99): an erased block means "chart defaults
+          # apply" instead of a vanished probe or an unhardened container.
+          # Never wrap these in an "if" - a guard hides the erased case
+          # completely instead of rendering a visible null.
+          livenessProbe:
+            {{- include "rss-bridge.livenessProbe" .Values.rssBridge.livenessProbe | nindent 12 }}
+          readinessProbe:
+            {{- include "rss-bridge.readinessProbe" .Values.rssBridge.readinessProbe | nindent 12 }}
+          startupProbe:
+            {{- include "rss-bridge.startupProbe" .Values.rssBridge.startupProbe | nindent 12 }}
+          resources:
+            {{- include "rss-bridge.effectiveResources" .Values.rssBridge.resources | nindent 12 }}
+          securityContext:
+            {{- include "rss-bridge.containerSecurityContext" .Values.rssBridge.securityContext | nindent 12 }}
+          volumeMounts:
+            - name: whitelist
+              mountPath: /app/whitelist.txt
+              subPath: whitelist.txt
+              readOnly: true
+            # The four writable paths below are what keeps
+            # readOnlyRootFilesystem: true possible. They are image facts
+            # rather than user configuration, so they are not values.
+            #
+            # They were found empirically, not guessed: the image was run with
+            # a writable root filesystem, exercised across every whitelisted
+            # bridge, and its diff layer read afterwards. Three of the four
+            # showed up that way. /tmp did NOT - PHP's opcache creates its lock
+            # file there and unlinks it immediately, so it never appears in a
+            # filesystem diff and only surfaced when the hardened container
+            # died at startup with "Unable to create lock file: Read-only file
+            # system". Stopping at the first writable path found would have
+            # shipped a chart that cannot start.
+            - name: cache
+              # RSS-Bridge's file cache. Not optional: the app checks the
+              # directory with is_writable() and throws on every feed request
+              # if it is not - while /?action=health still answers 200, so the
+              # probes would report a healthy pod that serves no feeds.
+              mountPath: /app/cache
+            - name: tmp
+              # PHP opcache lock file (created and immediately unlinked) and
+              # PHP's default upload temp dir.
+              mountPath: /tmp
+            - name: run
+              # nginx.pid
+              mountPath: /run
+            - name: run-php
+              # php-fpm's pid file and its fastcgi socket. Nested inside /run
+              # on purpose: the emptyDir above does not contain the php
+              # subdirectory the pool config expects, and php-fpm does not
+              # create it.
+              mountPath: /run/php
+            - name: nginx-lib
+              # nginx creates its body/fastcgi/proxy/scgi/uwsgi temp
+              # directories here at startup.
+              mountPath: /var/lib/nginx
+      volumes:
+        - name: whitelist
+          configMap:
+            name: "{{ .Release.Name }}-{{ .Chart.Name }}-configmap"
+        - name: cache
+          emptyDir: {}
+        - name: tmp
+          emptyDir: {}
+        - name: run
+          emptyDir: {}
+        - name: run-php
+          emptyDir: {}
+        - name: nginx-lib
+          emptyDir: {}
+      restartPolicy: Always

rss-bridge/templates/rss-bridge.ingress.yaml

@@ -0,0 +1,42 @@
+{{- if .Values.ingress.enabled }}
+{{- $hosts := required "At least one ingress host must be provided (ingress.hosts)" .Values.ingress.hosts }}
+{{- /* helm lint reports a failed required() but keeps rendering with an empty
+       string, which is not iterable. Anything but a list is coerced away here
+       so lint reports the missing value instead of a template stack trace; a
+       real render never reaches this, because required() aborts on nil and the
+       schema rejects every non-array. */ -}}
+{{- if not (kindIs "slice" $hosts) }}{{- $hosts = list }}{{- end }}
+{{- $tls := fromYaml (include "rss-bridge.tlsGroups" (dict "hosts" $hosts "root" $)) }}
+apiVersion: networking.k8s.io/v1
+kind: Ingress
+metadata:
+  name: {{ .Release.Name }}-{{ .Chart.Name }}-ingress
+  annotations:
+    cert-manager.io/cluster-issuer: {{ required "A Cluster-Issuer must be provided" .Values.ingress.clusterIssuer }}
+    {{- with .Values.ingress.annotations }}
+    {{- toYaml . | nindent 4 }}
+    {{- end }}
+spec:
+  ingressClassName: {{ .Values.ingress.className }}
+  rules:
+    {{- range $entry := $hosts }}
+    - host: {{ $entry.host }}
+      http:
+        paths:
+          - backend:
+              service:
+                name: {{ $.Release.Name }}-{{ $.Chart.Name }}-service
+                port:
+                  number: 80
+            path: /
+            pathType: Prefix
+    {{- end }}
+  tls:
+    {{- range $secret := $tls.order }}
+    - hosts:
+        {{- range $host := index $tls.groups $secret }}
+        - {{ $host }}
+        {{- end }}
+      secretName: {{ $secret }}
+    {{- end }}
+{{- end }}

rss-bridge/templates/rss-bridge.service.yaml

@@ -0,0 +1,15 @@
+apiVersion: v1
+kind: Service
+metadata:
+  name: {{ .Release.Name }}-{{ .Chart.Name }}-service
+spec:
+  selector:
+    app: {{ .Release.Name }}-{{ .Chart.Name }}-deployment
+  ports:
+    # Port 80 and the named targetPort are kept exactly as the manifest this
+    # chart replaces had them, so the takeover does not change how traffic
+    # reaches the container.
+    - protocol: TCP
+      port: 80
+      targetPort: rss-bridge-port
+  type: ClusterIP