Open source video conferencing app powered by LiveKit. Built with Django and React.
🔧(helm) point media services to Garage by default
briquet68fe3f96fcb6
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex ac6c60d7..7ffd29bb 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -42,6 +42,7 @@ and this project adheres to- ♻️(backend) decouple recording event handling from LiveKit egress statuses- ♻️(agents) replace the minio client by boto3- 🔧(compose) replace MinIO by Garage for local development+- 🔧(helm) point media services to Garage by default### Fixeddiff --git a/UPGRADE.md b/UPGRADE.mdindex 908428ff..be9f7a74 100644--- a/UPGRADE.md+++ b/UPGRADE.md@@ -16,6 +16,31 @@ the following command inside your docker container:## [Unreleased]+### Local development: MinIO replaced by Garage++The development stacks now use [Garage](https://garagehq.deuxfleurs.fr/) instead of MinIO as S3 storage. Garage keeps its own format in `data/media/meta` and `data/media/data` and cannot read what MinIO left there, so local recordings and files will be lost.++To migrate a local environment:++1. Stop the stack and remove its containers, including the former `minio` one: `docker compose down --remove-orphans`+2. Optionally reclaim the space used by MinIO: `rm -rf data/media && make data/media`+3. In your `env.d/development/*` files, replace `minio:9000` by `garage:9000`, the `meet` / `password` credentials by `meet-access-key` / `meet-secret-access-key`, and add `AWS_S3_REGION_NAME=local` (or delete these files and run `make create-env-files`)+4. Run `make create-env-files` to generate `env.d/development/garage`, which holds a random RPC secret for Garage.+5. Rebuild the images, since the summary and agent images now install boto3 instead of minio++### Summary service and metadata collector: boto3 replaces the minio client++The summary service and the metadata collector agent now talk to S3 through boto3 instead of the minio client, with the same settings.+Requests are now signed for `AWS_S3_REGION_NAME` as-is. When it is not set, the region is no longer looked up from the bucket: boto3 falls back to `AWS_DEFAULT_REGION`, then to `us-east-1`. If you left `AWS_S3_REGION_NAME` unset, set it to your provider's region before upgrading, or providers that check the signing region will reject the transcripts, summaries and meeting metadata uploads, as well as their signed URLs.++Also:+- Signed URLs to transcripts and summaries are now always path-style (`<endpoint>/<bucket>/<key>`), whereas the minio client used virtual-hosted-style URLs+- The metadata collector now accepts `AWS_S3_ENDPOINT_URL` with or without a scheme, like the summary service: the scheme always follows `AWS_S3_SECURE_ACCESS`.++### Helm chart: media services default to Garage++The `meet` chart now defaults `serviceMedia.host` and `serviceMediaFiles.host` to `garage.meet.svc.cluster.local`, and the `upstream-vhost` annotation of `ingressMedia` and `ingressMediaFiles` to `garage.meet.svc.cluster.local:9000`. If you relied on the former `minio.meet.svc.cluster.local` defaults, set these values explicitly to your S3 service before upgrading, or recordings and files stop being served under `/media`.+## v1.30.0### Removing S3 storage-event webhooks for recordingsdiff --git a/src/helm/meet/README.md b/src/helm/meet/README.mdindex a97a8627..23627cc2 100644--- a/src/helm/meet/README.md+++ b/src/helm/meet/README.md@@ -45,10 +45,10 @@| `ingressMedia.tls.additional[].hosts[]` | Hosts for additional TLS config | || `ingressMedia.annotations.nginx.ingress.kubernetes.io/auth-url` | | `https://meet.example.com/api/v1.0/recordings/media-auth/` || `ingressMedia.annotations.nginx.ingress.kubernetes.io/auth-response-headers` | | `Authorization, X-Amz-Date, X-Amz-Content-SHA256` |-| `ingressMedia.annotations.nginx.ingress.kubernetes.io/upstream-vhost` | | `minio.meet.svc.cluster.local:9000` |+| `ingressMedia.annotations.nginx.ingress.kubernetes.io/upstream-vhost` | | `garage.meet.svc.cluster.local:9000` || `ingressMedia.annotations.nginx.ingress.kubernetes.io/configuration-snippet` | | `add_header Content-Security-Policy "default-src 'none'" always;` |-| `serviceMedia.host` | | `minio.meet.svc.cluster.local` |+| `serviceMedia.host` | | `garage.meet.svc.cluster.local` || `serviceMedia.port` | | `9000` || `serviceMedia.annotations` | | `{}` |diff --git a/src/helm/meet/values.yaml b/src/helm/meet/values.yamlindex d661c653..48fec432 100644--- a/src/helm/meet/values.yaml+++ b/src/helm/meet/values.yaml@@ -128,7 +128,7 @@ ingressMedia:nginx.ingress.kubernetes.io/use-regex: "true"nginx.ingress.kubernetes.io/auth-url: https://meet.example.com/api/v1.0/recordings/media-auth/nginx.ingress.kubernetes.io/auth-response-headers: "Authorization, X-Amz-Date, X-Amz-Content-SHA256"- nginx.ingress.kubernetes.io/upstream-vhost: minio.meet.svc.cluster.local:9000+ nginx.ingress.kubernetes.io/upstream-vhost: garage.meet.svc.cluster.local:9000nginx.ingress.kubernetes.io/configuration-snippet: |add_header Content-Security-Policy "default-src 'none'" always;@@ -136,7 +136,7 @@ ingressMedia:## @param serviceMedia.port## @param serviceMedia.annotationsserviceMedia:- host: minio.meet.svc.cluster.local+ host: garage.meet.svc.cluster.localport: 9000annotations: {}@@ -171,7 +171,7 @@ ingressMediaFiles:nginx.ingress.kubernetes.io/use-regex: "true"nginx.ingress.kubernetes.io/auth-url: https://meet.example.com/api/v1.0/files/media-auth/nginx.ingress.kubernetes.io/auth-response-headers: "Authorization, X-Amz-Date, X-Amz-Content-SHA256"- nginx.ingress.kubernetes.io/upstream-vhost: minio.meet.svc.cluster.local:9000+ nginx.ingress.kubernetes.io/upstream-vhost: garage.meet.svc.cluster.local:9000nginx.ingress.kubernetes.io/configuration-snippet: |add_header Content-Security-Policy "default-src 'none'" always;add_header Content-Disposition "attachment";@@ -180,7 +180,7 @@ ingressMediaFiles:## @param serviceMediaFiles.port## @param serviceMediaFiles.annotationsserviceMediaFiles:- host: minio.meet.svc.cluster.local+ host: garage.meet.svc.cluster.localport: 9000annotations: {}