Dennis Paradzinski
6efce0c8f1
Some checks failed
deploy / deploy (push) Failing after 3s
Self-hosted Jitsi instance at meet.it.financeflow.de — avoids the meet.jit.si moderator-auth wall. Four components (web/prosody/jicofo/jvb) as raw k3s manifests, same deploy pattern as Embertime (Gitea Actions + kubectl apply + KUBECONFIG_B64 secret). JVB uses hostNetwork + UDP 10000 for media — requires router forward. Component passwords live in a kubectl-applied Secret (not in git); generate-secrets.sh produces a fresh manifest. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
27 lines
694 B
YAML
27 lines
694 B
YAML
# Focus/conference manager. Talks to prosody as a component, signs
|
|
# users into rooms, picks JVBs from the brewery for video routing.
|
|
apiVersion: apps/v1
|
|
kind: Deployment
|
|
metadata:
|
|
name: jicofo
|
|
namespace: jitsi
|
|
spec:
|
|
replicas: 1
|
|
strategy:
|
|
type: Recreate
|
|
selector:
|
|
matchLabels: { app: jicofo }
|
|
template:
|
|
metadata:
|
|
labels: { app: jicofo }
|
|
spec:
|
|
containers:
|
|
- name: jicofo
|
|
image: jitsi/jicofo:stable
|
|
envFrom:
|
|
- configMapRef: { name: jitsi-config }
|
|
- secretRef: { name: jitsi-secrets }
|
|
resources:
|
|
requests: { cpu: 50m, memory: 256Mi }
|
|
limits: { cpu: 500m, memory: 1Gi }
|