From 614f5b91d910bfde2c89f2adac7e22b1f441ff80 Mon Sep 17 00:00:00 2001 From: Cedric Verstraeten Date: Tue, 13 Aug 2024 11:13:29 +0200 Subject: [PATCH] add docker readme + complete docs --- README.docker.md | 3 +++ README.md | 4 +++- 2 files changed, 6 insertions(+), 1 deletion(-) create mode 100644 README.docker.md diff --git a/README.docker.md b/README.docker.md new file mode 100644 index 0000000..dd4faaa --- /dev/null +++ b/README.docker.md @@ -0,0 +1,3 @@ +# Self-hosted with Docker Compose + +.... diff --git a/README.md b/README.md index bef7c7b..5dd42c7 100644 --- a/README.md +++ b/README.md @@ -16,7 +16,9 @@ Self-hosted deployments are typically used for camera processing and edge storag ![Self-hosted deployment](./assets/images/deployment-self-hosted.svg) -Follow the deployment guides for each Kubernetes distro: +A key aspect of this deployment is the scaling of Kerberos Agents. Each camera is assigned a dedicated Kerberos Agent container, which is linked to a central Kerberos Vault. The Kerberos Vault stores metadata in MongoDB, recordings in Minio (or another S3-compliant object storage), and can generate events in a message broker like RabbitMQ. This approach enables you to develop custom applications/logic that can respond to the creation of new recordings. + +Based on your technology experience and preferences, you can choose from the following deployment guides: - [Install Kerberos.io on Microk8s](/README.microk8s.md) - [Install Kerberos.io on Kubernetes](/README.k8s.md)