diff options
| -rw-r--r-- | f3s/protonbridge/helm-chart/templates/deployment.yaml | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/f3s/protonbridge/helm-chart/templates/deployment.yaml b/f3s/protonbridge/helm-chart/templates/deployment.yaml index 833a810..4f6bb64 100644 --- a/f3s/protonbridge/helm-chart/templates/deployment.yaml +++ b/f3s/protonbridge/helm-chart/templates/deployment.yaml @@ -72,15 +72,17 @@ spec: mountPath: /bridge-data containers: - name: protonbridge - # Bridge v3 CLI kept open with an attachable TTY so it can run headlessly. + # Bridge v3 daemon. IMAP and SMTP stay available while account management + # is performed through a separate CLI process. # # Session persists in pass on NFS PVC; subsequent restarts reconnect automatically. # # ACCOUNT LOGIN (when Bridge reports no active accounts): # 1. Get pod name: kubectl get pod -n services -l app=protonbridge - # 2. Attach to the Bridge CLI: kubectl attach -it -n services <pod-name> + # 2. Start a CLI connected to the daemon: + # kubectl exec -it -n services <pod-name> -- protonmail-bridge --cli # 3. At the bridge> prompt, type 'login' and follow the prompts - # 4. Type 'quit'; the pod restarts and reconnects with the saved session + # 4. Type 'quit'; only the separate CLI exits # # EMAIL CLIENT SETUP (after login): # IMAP: <any-r-vm-lan-ip>:30143, STARTTLS, accept self-signed cert @@ -88,8 +90,6 @@ spec: # Username: your ProtonMail address # Password: bridge-generated password (from 'info' in the CLI above) image: shenxn/protonmail-bridge:latest - stdin: true - tty: true command: - /bin/bash - -c @@ -100,7 +100,7 @@ spec: apt-get install -y -qq --no-install-recommends libfido2-1 socat TCP-LISTEN:25,fork TCP:127.0.0.1:1025 & socat TCP-LISTEN:143,fork TCP:127.0.0.1:1143 & - exec protonmail-bridge --cli + exec protonmail-bridge --noninteractive env: - name: GNUPGHOME value: /bridge-data/.gnupg |