diff --git a/static/images/prologue/deployments/cloud-less-then-5.svg b/content/prologue/deployments/cloud-less-then-5.svg similarity index 100% rename from static/images/prologue/deployments/cloud-less-then-5.svg rename to content/prologue/deployments/cloud-less-then-5.svg diff --git a/static/images/prologue/deployments/cloud-more-then-5.svg b/content/prologue/deployments/cloud-more-then-5.svg similarity index 100% rename from static/images/prologue/deployments/cloud-more-then-5.svg rename to content/prologue/deployments/cloud-more-then-5.svg diff --git a/content/prologue/deployments/deployment-hub-vault.svg b/content/prologue/deployments/deployment-hub-vault.svg new file mode 100644 index 0000000..a80e6c8 --- /dev/null +++ b/content/prologue/deployments/deployment-hub-vault.svg @@ -0,0 +1,637 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/content/prologue/deployments/deployment-hub.svg b/content/prologue/deployments/deployment-hub.svg new file mode 100644 index 0000000..8ad5a80 --- /dev/null +++ b/content/prologue/deployments/deployment-hub.svg @@ -0,0 +1,655 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/content/prologue/deployments.md b/content/prologue/deployments/index.md similarity index 81% rename from content/prologue/deployments.md rename to content/prologue/deployments/index.md index 3867dc7..08e5af4 100644 --- a/content/prologue/deployments.md +++ b/content/prologue/deployments/index.md @@ -31,19 +31,19 @@ If you have a limited number of surveillance cameras you would like to monitor, On below architecture, a couple of Kerberos agents are installed on-premise (inside the local network). A Kerberos agent is installed for each surveillance camera, and each Kerberos agent runs on a seperate host (Raspberry Pi, VM, etc). The web interface of the Kerberos agents can be reached from the internal network, but cannot be accessed from the cloud. - +{{< figure src="onpremise-less-then-5.svg" alt="Having just a single or two camera(s) to be monitored then Kerberos Opensource might be the right choice." caption="Having just a single or two camera(s) to be monitored then Kerberos Opensource might be the right choice." class="stretch">}} Another option to install the Kerberos Open Source agent is to use Docker. Instead of having seperate hosts for each Kerberos agent, you will have a single host (Docker host) with multiple Docker containers. A Docker container is deployed for each surveillance camera, which contains the software to run the Kerberos agent. -Running your Kerberos agents inside Docker containers, allows you to process multiple surveilllance cameras using only one host. +Running your Kerberos agents inside Docker containers, allows you to process multiple surveillance cameras using only one host. - +{{< figure src="onpremise-less-then-5-docker.svg" alt="Having just a few of cameras to be monitored then Kerberos Opensource with Docker might be the right choice." caption="Having just a few of cameras to be monitored then Kerberos Opensource with Docker might be the right choice." class="stretch">}} ### More than 5 cameras When working within an enterprise context, where you require high availability and have a large amount of surveillance cameras being monitored, [Kerberos Enterprise](/enterprise/first-things-first) is a good choice. Im comparison to the Open Source version, Kerberos Enterprise uses Kubernetes to help you scale (and secure) your video surveillance landscape. Kerberos agents, or Kubernetes deployments, are deployed inside your cluster and load balanced over the different nodes. When a Kerberos agent dies, or the node on which the deployment is running, Kubernetes will reschedule it to another healthy node. - +{{< figure src="onpremise-more-then-5.svg" alt="When you start having bigger deployments it's recommended to go with a Kubernetes approach." caption="When you start having bigger deployments it's recommended to go with a Kubernetes approach." class="stretch">}} ## Agents in the cloud @@ -57,13 +57,13 @@ When setting up a VPN connection you will expose your surveillance cameras to yo If you have a limited number of surveillance cameras you would like to monitor, and don't have any high availability requirements, the Kerberos Open Source agent is a good choice. You can install the Kerberos Open Source agent on Docker. Instead of having seperate VM's for each Kerberos agent, you will have a single VM (Docker host) with multiple Docker containers. A Docker container is deployed for each surveillance camera, which contains the software to run the Kerberos agent. - +{{< figure src="cloud-less-then-5.svg" alt="By using port forwarding or a VPN tunnel you can start processing your camera streams in the cloud." caption="By using port forwarding or a VPN tunnel you can start processing your camera streams in the cloud." class="stretch">}} ### More than 5 cameras Similar to [Kerberos Enterprise](/enterprise/first-things-first) on-premise, you can run the a Kubernetes in the cloud. The exact same solution is available, only the way how you connect to your video surveillance cameras will be different, as they will probably live in a different network. To make this work you will need to setup a VPN tunnel (or whatever your security teams have defined as a back practice). When [Kerberos Enterprise](/enterprise/introduction) is deployed to the cloud, it can be used any where. Public cloud (AWS, Google, Azure, etc) or private cloud. You can run it where you want. - +{{< figure src="cloud-more-then-5.svg" alt="As previous mentioned you could process them in a Kubernetes cluster in the cloud." caption="As previous mentioned you could process them in a Kubernetes cluster in the cloud." class="stretch">}} ## Kerberos Hub @@ -96,4 +96,4 @@ As soon as the recording is successfully received several engines will be execut By using a browser you can navigate to Kerberos Hub, and review all the recordings made by the Kerberos agents on-premise. On top of that you will receive more context about the recordings, get notifications, view a livestream and much more. Read more about [Kerberos Hub](/hub/first-things-first). - +{{< figure src="deployment-hub-vault.svg" alt="As previous mentioned you could process them in a Kubernetes cluster in the cloud." caption="As previous mentioned you could process them in a Kubernetes cluster in the cloud." class="stretch">}} \ No newline at end of file diff --git a/static/images/prologue/deployments/onpremise-less-then-5-docker.svg b/content/prologue/deployments/onpremise-less-then-5-docker.svg similarity index 100% rename from static/images/prologue/deployments/onpremise-less-then-5-docker.svg rename to content/prologue/deployments/onpremise-less-then-5-docker.svg diff --git a/static/images/prologue/deployments/onpremise-less-then-5.svg b/content/prologue/deployments/onpremise-less-then-5.svg similarity index 100% rename from static/images/prologue/deployments/onpremise-less-then-5.svg rename to content/prologue/deployments/onpremise-less-then-5.svg diff --git a/static/images/prologue/deployments/onpremise-more-then-5.svg b/content/prologue/deployments/onpremise-more-then-5.svg similarity index 100% rename from static/images/prologue/deployments/onpremise-more-then-5.svg rename to content/prologue/deployments/onpremise-more-then-5.svg diff --git a/static/images/prologue/agent-explanation.svg b/content/prologue/how/agent-explanation.svg similarity index 100% rename from static/images/prologue/agent-explanation.svg rename to content/prologue/how/agent-explanation.svg diff --git a/static/images/prologue/deployment-hub.svg b/content/prologue/how/deployment-hub.svg similarity index 100% rename from static/images/prologue/deployment-hub.svg rename to content/prologue/how/deployment-hub.svg diff --git a/static/images/prologue/deployment-vault.svg b/content/prologue/how/deployment-vault.svg similarity index 100% rename from static/images/prologue/deployment-vault.svg rename to content/prologue/how/deployment-vault.svg diff --git a/content/prologue/how.md b/content/prologue/how/index.md similarity index 83% rename from content/prologue/how.md rename to content/prologue/how/index.md index 250409d..455e606 100644 --- a/content/prologue/how.md +++ b/content/prologue/how/index.md @@ -15,7 +15,7 @@ toc: true When you install Kerberos Open Source or Kerberos Enterprise we will refer to it as the Kerberos Agent. A Kerberos Agent, is a software solution that consist of two pieces: Front-End and Back-End. The Back-End processes the video stream of a single surveillance camera, makes recordings and takes actions (for example sending notifications). The Front-End allows you to review recordings, and configure the Back-End. - +{{< figure src="agent-explanation.svg" alt="A Kerberos agent consists of both a backend en frontend." caption="A Kerberos agent consists of both a backend en frontend." class="stretch">}} ## Front-End The Kerberos Agent ships with a web interface (Front-End) and a video processing engine (Back-End). The Front-End allows the user to modify specific settings, and if Kerberos Open Source, watch recordings in a easy-to-use interface; The Front-End for [Kerberos Enterprise](/enterprise/introduction) is only for configuration purposes only. @@ -31,7 +31,7 @@ The Kerberos project started as an Open Source project, with a main focus on low Enterprises are more demanding, and have a lot of surveillance cameras, therefore they need a scalable surveillance system. The [Enterprise edition](/enterprise/introduction) of Kerberos allows you to operate a video surveillance cluster (Kubernetes) on-premise or in the cloud (AWS/GCP/Azure). - +{{< figure src="opensource-vs-enterprise-agent.svg" alt="The different deployment options for Opensource and Enterprise agent." caption="The different deployment options for Opensource and Enterprise agent." class="stretch">}} The Open Source and Enterprise edition are significantly different from a source code point of view. The [Enterprise edition](/enterprise/introduction) is a complete rewrite of the Open Source version, and got all the best practices we discovered over the years implemented. Both version are and will remain updated in the future. @@ -45,10 +45,10 @@ On the other hand if you plan to manage a larger network of surveillance cameras In addition to the concept of BYOC, Kerberos Vault enables you to connect to Kerberos Cloud (with your own storage), send events to message brokers (such as Kafka or SQS) and enables you to build custom apps or services (such as a custom machine learning service). - +{{< figure src="deployment-vault.svg" alt="Kerberos Vault allows you to bring your own storage, and build extensions and integrations." caption="Kerberos Vault allows you to bring your own storage, and build extensions and integrations." class="stretch">}} ## Kerberos Hub When installing a Kerberos Agent inside your local network, it's possible to review your activity by using the agent its web interface. By all network principles, having a local setup, you will not be able to access the web interface from the cloud (outside your local network). On top of that, the Kerberos Agent doesn't come with a consolidated overview. This means that you will need to open multiple web interfaces, one for each connected surveillance camera. To simplify and resolve all of these challenges, [Kerberos Cloud](/cloud) was developed. - \ No newline at end of file +{{< figure src="deployment-hub.svg" alt="A Kerberos agent consists of both a backend en frontend." caption="A Kerberos agent consists of both a backend en frontend." class="stretch">}} \ No newline at end of file diff --git a/static/images/prologue/opensource-vs-enterprise-agent.svg b/content/prologue/how/opensource-vs-enterprise-agent.svg similarity index 100% rename from static/images/prologue/opensource-vs-enterprise-agent.svg rename to content/prologue/how/opensource-vs-enterprise-agent.svg diff --git a/content/prologue/introduction.md b/content/prologue/introduction/index.md similarity index 100% rename from content/prologue/introduction.md rename to content/prologue/introduction/index.md diff --git a/content/prologue/quick-start.md b/content/prologue/quick-start/index.md similarity index 100% rename from content/prologue/quick-start.md rename to content/prologue/quick-start/index.md