From c19725b5c6f7facd87dc0d3cb97a8284c9959bd4 Mon Sep 17 00:00:00 2001
From: Paul Buetow <paul@buetow.org>
Date: Tue, 30 Jun 2026 08:48:24 +0300
Subject: f3s/ychat: drop TCP probes (crash on empty open+close)

---
 f3s/ychat/helm-chart/templates/deployment.yaml | 15 +++------------
 1 file changed, 3 insertions(+), 12 deletions(-)

diff --git a/f3s/ychat/helm-chart/templates/deployment.yaml b/f3s/ychat/helm-chart/templates/deployment.yaml
index 53f8443..5b5a4d1 100644
--- a/f3s/ychat/helm-chart/templates/deployment.yaml
+++ b/f3s/ychat/helm-chart/templates/deployment.yaml
@@ -35,18 +35,9 @@ spec:
           ports:
             - containerPort: 2000
               name: http
-          # yChat speaks HTTP/0.9-style responses (no status line), so an
-          # httpGet probe would never succeed. Use a TCP socket probe instead.
-          livenessProbe:
-            tcpSocket:
-              port: http
-            initialDelaySeconds: 5
-            periodSeconds: 15
-          readinessProbe:
-            tcpSocket:
-              port: http
-            initialDelaySeconds: 3
-            periodSeconds: 10
+          # No liveness/readiness probes: yChat segfaults on an empty TCP
+          # open+close (a TCP-socket probe would kill it). It serves real HTTP
+          # requests fine, and kubelet restarts the pod if the process exits.
           resources:
             requests:
               memory: 32Mi
-- 
cgit v1.2.3