Releases: kerberos-io/vault
v1.0.5
v1.0.4
- When forwarding recordings from one Kerberos Vault to another Kerberos Vault, it might happen that the file was uploaded to the designated storage provider but silently fail. This can cause the recording being labeled as "not" forward, and will trigger the upload again. When setting specific policies on the storage provider (e.g. google cloud storage), the storage provider might refuse the new upload, which will result in an endless loop. The latter was fixed, but it still created duplicate messages, as the integration was still being executed. Now when we have a duplicate file, we should stop, and create no additional messages.
- Have the possibility to define multiple concurrent queues. This means that on uploading of a recording we will create multiple messages in various queues at the same time.
- Docker Hub image repository was changed we moved to
uugai/vault.
1.0.1398121865
Changes
- Bucket policy GCP: When the bucket retention period on Google Cloud Storage was turned on, and a file with the same path does exists, an error is thrown mentioning the file was not allowed to be overwritten due to the policy. This issue was fixed before, however under specific circumstances that issues still occurs. This is now resolved, and recordings are flagged as uploaded and removed from the queue.
- Optimisation multi replica forwarding: we have optimised the processed of distributing recordings to various replicas, minimising the change of overlap of forwarding the recording multiple times.
Release
- Docker Hub
- kerberos/vault:1.0.1398121865
1.0.1389072349
Changes
- Fix cleanup: When setting up multiple accounts with different retention periods, pointing to the same provider. Media was removed taking into account the lowest retention period.
Release
- Docker Hub
- kerberos/vault:1.0.1389072349
1.0.1311840093
Changes
- Fix Kafka integration: an certification issue was blocking specific Kafka brokers to properly connect.
Release
- Docker Hub
- kerberos/vault:1.0.1311840093
1.0.1307193313
Changes
- Fix forwarding: Cloud storage policies prevent overwriting a specific file will cause infinite retry loop. We now catch the error and mark the media as being forwarded.
- Fix forwarding: Concurrent forwarding optimisation, we are now uploading recordings concurrently. Instead of forwarding media one by one, we are now uploading in bulks of 10.
- Fix forwarding: timeout between two forwardings is now configurable through an environment variable
CONTINUOUS_TIMEOUT. - Fix forwarding: an issue with horizantal scaling was resolved. Multiple workers (pods/containers) were uploading the same recordings and not properly synchronised.
Release
- Docker Hub
- kerberos/vault:1.0.1307193313
1.0.1218231161
Changes
- Added a new endpoint to upload large files (multipart), required for uploading zip files of GBs.
Release
- Docker Hub
- kerberos/vault:1.0.1218231161
1.0.1189510652
Changes
- Support for AMQPS (previously only AMQP was allowed), we now support managed services like AWS Rabbitmq.
Release
- Docker Hub
- kerberos/vault:1.0.1189510652
1.0.1022292048
Changes
- Move thumbnail generation to FFMPEG.
- Provide ARM64 build
- Fix camera page, stopped loading
Release
- Docker Hub
- kerberos/vault:1.0.1022292048
1.0.817949156
Changes
- Merged API and Frontend projects (similar to Kerberos Agent and Kerberos Factory), we no longer require two ingresses and two ports (see migration section).
- Update UI components, add mobile menu and sidebar fixes.
- Add health checks
Migration
We have merged the API and Frontend into a single binary (similar to Kerberos Agent). Previously we had two applications served in the Kerberos Vault container 8081 and 80. Now both the API and Frontend are served through a single binary running on port 80.
As Kerberos Vault is a middleware, and it connects to both Kerberos Agents as Kerberos Hub it's a bit more cautious. As we have merged into a single port, we will no longer need two endpoints. Previously we had http://yourdomain.com and http://api.yourdomain.com, now we only operate with the base url http://yourdomain.com, and a suffix for the API http://yourdomain.com/api.
To migrate to this new setup you you can use the new deployment.yaml file or docker-compose.yaml. You'll notice we have removed the additional port 8081 and the ingresses. Once you have the new deployment ready, you'll need both the Kerberos Agents and Kerberos Hub to point to the new API url of Kerberos Vault: http://yourdomain.com/api.
Release
- Docker Hub
- kerberos/vault:1.0.817949156