From d4ed3eb73c730e9fc441f64e5ada8c1d7cdc35b7 Mon Sep 17 00:00:00 2001 From: SmokyZone Date: Fri, 18 Sep 2026 20:25:19 +0200 Subject: [PATCH] Override BAO_ADDR to https now that TLS is enabled MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The chart hardcodes BAO_ADDR=http://127.0.0.1:8200 for its own readiness/liveness probe CLI calls. With TLS enabled this made the pod 永远 NotReady ('Client sent an HTTP request to an HTTPS server'). Override via server.extraEnvironmentVars (Kubernetes uses last-wins for duplicate env var names). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- values.yaml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/values.yaml b/values.yaml index f94e0ba..280c7cc 100644 --- a/values.yaml +++ b/values.yaml @@ -56,6 +56,13 @@ openbao: cpu: 500m memory: 512Mi + # The chart hardcodes BAO_ADDR=http://127.0.0.1:8200 for internal CLI + # calls (readiness/liveness probes, etc.). Override it now that the + # listener speaks TLS, otherwise the pod never becomes Ready. + extraEnvironmentVars: + BAO_ADDR: https://127.0.0.1:8200 + BAO_SKIP_VERIFY: "true" + ui: enabled: true # NodePort, same pattern as ArgoCD (30080/30443) and Gitea (30300):