2026-10-13 12:36:59 +02:00
4 changed files with 18 additions and 9 deletions
@@ -28,9 +28,13 @@
 # in the job. Since that PR's rendered defaults are byte-identical to
 # origin/main, the chart is ruled out as the cause and the runner is the
 # implicated layer - which is where #51 had already placed it. It reproduced
-# on every run of that branch since, so it is not a fluke; but nobody has
-# identified what changed on the runner, so #51 is not closed on the strength
-# of a colour.
+# on every run of that branch since, so it is not a fluke, and #51 was closed
+# on that round. What was NEVER identified is the cause: nobody established
+# what changed on the runner, and the diagnostic programme in that issue
+# (docker info for userns and the dind configuration, the same image in a
+# local k3d without remapping) was not executed. So if this chart's
+# install-test goes red again, that is a fresh finding and not a known quirk -
+# and this comment is the context it should be read against.
 #
 # Either way this overlay stays load-bearing: the install-test installs the
 # INGRESS mode (that is what the fixture sets), so the Gateway mode of this
@@ -5,7 +5,7 @@ icon: https://raw.githubusercontent.com/RSS-Bridge/rss-bridge/master/static/logo

 type: application

-version: 2.1.0+up2026.09.30
+version: 2.1.1+up2026.09.30
 appVersion: "2026-09-30"

 maintainers:
@@ -2,8 +2,11 @@
 The Gateway-API alternative to rss-bridge.ingress.yaml (Gitea #114), and the
 LAST chart of that sweep: 22 charts carried an Ingress template and 21 an
 HTTPRoute template, and the difference was this one. It was held back because
-its install-test fails on the Gitea runner (#51), not for anything about its
-shape.
+its install-test had been failing on the Gitea runner (#51), not for anything
+about its shape - and that test went green in the very PR that converted it,
+on a render byte-identical to main, which is what ruled the chart out and left
+the runner. #51 was closed on the strength of that round; the cause was never
+identified, so a recurrence is a fresh finding rather than a known quirk.

 WHAT THIS RENDERS, AND WHAT IT DELIBERATELY DOES NOT

@@ -272,9 +272,11 @@ ingress:
 # THE GATEWAY-API ALTERNATIVE TO THE INGRESS ABOVE (Gitea #114), and this chart
 # is the LAST of that sweep - 22 charts carried an Ingress template, 21 an
 # HTTPRoute template, and the difference was this one. It was held back because
-# its install-test fails on the Gitea runner (#51), not for anything about its
-# shape, and that test is still red: the failure is a known, bounded
-# environment defect and no finding about this mode.
+# its install-test had been failing on the Gitea runner (#51), not for anything
+# about its shape - and that test went green in the very PR that converted it,
+# on a render byte-identical to main, which ruled the chart out and left the
+# runner. #51 was closed on that round; the cause was never identified, so a
+# recurrence is a fresh finding rather than a known quirk.
 #
 # Off by default, so an existing release is unaffected. Mutually exclusive with
 # ingress.enabled - the render aborts when both are true, naming both value