From 818a71f7b6af8a0412718bb737cf12a541030000 Mon Sep 17 00:00:00 2001
From: jklein <github@justin-klein.de>
Date: Sun, 23 Aug 2026 00:30:26 +0200
Subject: [PATCH] Clean up stale ip rules on gluetun container start

An uncleanly exited gluetun leaves its ip rule in the shared pod
network namespace; the restarted container then fails forever with
'adding ip rule 101: file exists' while the kill switch keeps blocking
all egress. Apply the upstream-recommended Kubernetes fix: a postStart
hook dropping table-51820 rules.
---
 freesailarr/templates/freesailarr.sfs.yaml | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/freesailarr/templates/freesailarr.sfs.yaml b/freesailarr/templates/freesailarr.sfs.yaml
index a7ed34e..3bf1335 100644
--- a/freesailarr/templates/freesailarr.sfs.yaml
+++ b/freesailarr/templates/freesailarr.sfs.yaml
@@ -27,6 +27,17 @@ spec:
         - name: gluetun
           image: "qmcgaw/gluetun:{{ .Chart.AppVersion }}"
           imagePullPolicy: IfNotPresent
+          # An uncleanly exited gluetun (crash, OOM, node issue) leaves its ip
+          # rule behind in the shared pod network namespace, and the restarted
+          # container then fails forever with "ip rule 101 ... file exists".
+          # Upstream-recommended fix for Kubernetes: drop stale rules on start.
+          lifecycle:
+            postStart:
+              exec:
+                command:
+                  - /bin/sh
+                  - -c
+                  - (ip rule del table 51820; ip -6 rule del table 51820) || true
           env:
             - name: TZ
               value: {{ .Values.timezone | quote }}