From f700f74a4c9aa9c79902fa49195064a2e58a0192 Mon Sep 17 00:00:00 2001 From: Justin Klein Date: Wed, 14 Oct 2026 23:21:15 +0000 Subject: [PATCH] Charts: rss-bridge is not the Gateway sweep's exception any more The page still named 21 charts with one exception, rss-bridge, "frozen for changes". Both halves are stale: the freeze from Gitea #51 was lifted deliberately, the chart was converted in Gitea #124, and #114 closed with it. Measured on main instead of counted from memory: 22 charts carry an Ingress template and 22 carry an HTTPRoute template, so no exception is left. Two agents reported this while working on other issues and correctly left it alone rather than editing another issue's documentation inside theirs. --- Charts.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Charts.md b/Charts.md index 6be6033..d31971c 100644 --- a/Charts.md +++ b/Charts.md @@ -10,7 +10,7 @@ grep -E '^(version|appVersion):' /Chart.yaml ``` -**The "Ingress" column describes the Ingress mode only.** Since the Gateway-API sweep finished (Gitea #114), **every chart with a routing object also offers `httpRoute.enabled` as the mutually exclusive alternative** — 21 charts, the one exception being [rss-bridge](rss-bridge), which is frozen for changes. So that column says how a chart publishes *while the Ingress is the active mode*; it is not a claim that the Ingress is the only mode. The Gateway shapes differ more than the column suggests — two objects for [keycloak](keycloak) (public + admin) and [matrix-synapse](matrix-synapse) (homeserver + delegation), one per host entry for [homeassistant](homeassistant), one per app or one shared for [freesailarr](freesailarr) — and what each mode costs its chart is on the chart's own page under "Routing: Ingress or Gateway API". The convention is [style guide §4](Chart-Style-Guide#4-ingress-and-gateway-api). +**The "Ingress" column describes the Ingress mode only.** Since the Gateway-API sweep finished (Gitea #114), **every chart with a routing object also offers `httpRoute.enabled` as the mutually exclusive alternative** — **all 22 of them, with no exception.** [rss-bridge](rss-bridge) was the last one and read as the exception for a while, because Gitea #51 had frozen it after its install-test began failing on the runner; that freeze was lifted deliberately, the chart was converted in Gitea #124, and #114 closed with it. Measured on `main` rather than counted from memory: 22 charts carry an Ingress template and 22 carry an HTTPRoute template. So that column says how a chart publishes *while the Ingress is the active mode*; it is not a claim that the Ingress is the only mode. The Gateway shapes differ more than the column suggests — two objects for [keycloak](keycloak) (public + admin) and [matrix-synapse](matrix-synapse) (homeserver + delegation), one per host entry for [homeassistant](homeassistant), one per app or one shared for [freesailarr](freesailarr) — and what each mode costs its chart is on the chart's own page under "Routing: Ingress or Gateway API". The convention is [style guide §4](Chart-Style-Guide#4-ingress-and-gateway-api). **Every chart ships a `NetworkPolicy`, on by default** (Gitea #5), so that is not listed per row either — it would be the same word thirty times. What differs per chart is which of its ports can be restricted and what its egress rule costs, and that is on each chart's own page under `networkPolicy`. Two shapes are worth knowing before reading any of them: a port a **network** probe addresses stays open inside the cluster (the kubelet probes from the worker node's IP, which no chart can know), and `policyTypes` names only what there is something to restrict — so [valkey](valkey), [homeassistant](homeassistant) and [satisfactory](satisfactory) are Ingress-only, each for its own reason. The convention is [style guide §15](Chart-Style-Guide#15-networkpolicies).