Modularize bridge and improve control GUI

2026-08-03 00:55:12 +02:00
parent 73b302a965
commit f4ab49e0c8
26 changed files with 3104 additions and 1953 deletions
@@ -0,0 +1,37 @@
+# Kubernetes Examples
+
+This directory contains two deployment patterns for one Frigate instance.
+
+## Same Pod
+
+`same-pod.yaml` runs Frigate and the bridge as two containers in one Pod:
+
+- `camera-control` is a real sidecar,
+- both containers share the Pod network namespace,
+- `FRIGATE_URL=http://127.0.0.1:5000`,
+- this is the lowest-latency and simplest option when the bridge lifecycle
+  should follow the Frigate Pod.
+
+```bash
+kubectl apply -f examples/kubernetes/same-pod.yaml
+```
+
+For an existing Frigate Deployment, copy only the `camera-control` container
+block into the existing Pod template and keep `FRIGATE_URL` pointed at
+`http://127.0.0.1:5000`.
+
+## Two Pods
+
+`two-pods.yaml` runs Frigate and the bridge as separate Deployments:
+
+- Frigate is exposed through a Kubernetes Service named `frigate`,
+- the bridge uses `FRIGATE_URL=http://frigate:5000`,
+- the bridge has its own lifecycle and can be restarted independently,
+- this is useful when adding the bridge next to an existing Frigate Deployment.
+
+```bash
+kubectl apply -f examples/kubernetes/two-pods.yaml
+```
+
+For production, replace image names, storage, device access, resource requests,
+and secret names with values from your cluster.