jitsi-meet/infra/k3s/70-ingress.yaml
Dennis Paradzinski 6efce0c8f1
Some checks failed
deploy / deploy (push) Failing after 3s
chore: initial Jitsi-Meet k3s scaffold for darkemberserver
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>
2026-05-11 12:55:29 +02:00

31 lines
911 B
YAML

# TLS termination via cert-manager — same `letsencrypt-prod` ClusterIssuer
# as embertime/gitea. Traffic forwarded to jitsi-web on :80. JVB media
# (UDP 10000) goes around the ingress entirely (hostNetwork on the node).
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: jitsi
namespace: jitsi
annotations:
cert-manager.io/cluster-issuer: letsencrypt-prod
nginx.ingress.kubernetes.io/proxy-body-size: "0"
nginx.ingress.kubernetes.io/proxy-read-timeout: "3600"
nginx.ingress.kubernetes.io/proxy-send-timeout: "3600"
spec:
ingressClassName: nginx
tls:
- hosts:
- meet.it.financeflow.de
secretName: jitsi-tls
rules:
- host: meet.it.financeflow.de
http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: jitsi-web
port:
number: 80