diff --git a/config/_default/menus.toml b/config/_default/menus.toml
index fdfb285..b131a2d 100644
--- a/config/_default/menus.toml
+++ b/config/_default/menus.toml
@@ -4,43 +4,42 @@
identifier = "prologue"
url = "/prologue/"
-[[opensource]]
- name = "Opensource"
- weight = 11
- identifier = "opensource"
- url = "/opensource/"
-
[[agent]]
name = "Agent"
- weight = 12
+ weight = 11
identifier = "agent"
url = "/agent/"
[[enterprise]]
name = "Enterprise"
- weight = 13
+ weight = 12
identifier = "enterprise"
url = "/enterprise/"
-
[[factory]]
name = "Factory"
- weight = 14
+ weight = 13
identifier = "factory"
url = "/factory/"
[[vault]]
name = "Vault"
- weight = 15
+ weight = 14
identifier = "vault"
url = "/vault/"
[[hub]]
name = "Hub"
- weight = 16
+ weight = 15
identifier = "hub"
url = "/hub/"
+[[opensource]]
+ name = "Open Source (deprecated)"
+ weight = 16
+ identifier = "opensource"
+ url = "/opensource/"
+
[[main]]
name = "Homepage"
url = "https://kerberos.io"
diff --git a/content/_index.md b/content/_index.md
index bd6f935..b9a2467 100644
--- a/content/_index.md
+++ b/content/_index.md
@@ -41,7 +41,7 @@ Kerberos.io is a video analytics and monitoring platform, that is focussing on b
{{< figure src="kerberos-agent-edge.svg" alt="A Kerberos Agent is monitoring a single camera stream." caption="A Kerberos Agent is monitoring a single camera stream." class="stretch">}}
-With Kerberos.io you start small with one or more [Kerberos Agents](/opensource/first-things-first/), and grow over time while introducing more and more components like [Kerberos Factory](/factory/first-things-first/), [Kerberos Vault](/vault/first-things-first/) and [Kerberos Hub](/hub/first-things-first/), which is also referred to as the [Kerberos Enterprise Suite](/enterprise/first-things-first/). Kerberos.io is shipped through the concept of container technology such as Docker and Kubernetes, and implements the ideas of bring your own cloud, bring your own storage and bring your own technology.
+With Kerberos.io you start small with one or more [Kerberos Agents](/agent/first-things-first/), and grow over time while introducing more and more components like [Kerberos Factory](/factory/first-things-first/), [Kerberos Vault](/vault/first-things-first/) and [Kerberos Hub](/hub/first-things-first/), which is also referred to as the [Kerberos Enterprise Suite](/enterprise/first-things-first/). Kerberos.io is shipped through the concept of container technology such as Docker and Kubernetes, and implements the ideas of bring your own cloud, bring your own storage and bring your own technology.
{{< figure src="./kerberos-global.svg" alt="A scalable video platform for an ever-growing video landscape." caption="A scalable video platform for an ever-growing video landscape." class="stretch">}}
diff --git a/content/agent/first-things-first/index.md b/content/agent/first-things-first/index.md
new file mode 100644
index 0000000..dd5e75c
--- /dev/null
+++ b/content/agent/first-things-first/index.md
@@ -0,0 +1,22 @@
+---
+title: "First things first"
+description: "Kerberos Agent is an efficient video surveillance agent"
+lead: "Kerberos Agent is an efficient video surveillance agent"
+date: 2020-10-06T08:49:31+00:00
+lastmod: 2020-10-06T08:49:31+00:00
+draft: false
+images: []
+menu:
+ agent:
+ parent: "agent"
+weight: 201
+toc: true
+---
+
+Kerberos Agent is a cutting edge video surveillance management system made available as Open Source under the MIT License. This means that all the source code is available for you or your company, and you can use, transform and distribute the source code; as long you keep a reference of the original license. Kerberos Agent can be used for commercial usage (which was not the case for v2). Read more about the license here.
+
+## Introduction
+
+Kerberos.io applies the concept of agents. An agent is running next to or on your camera, and is processing a single camera feed. It applies motion based recording and make those recordings available through a user friendly web interface. Kerberos Agent allows you to connect to other cloud services or custom applications. Kerberos Agent is perfect for personal usage and/or is a great tool if you only have a couple of surveillance cameras to be processed.
+
+
\ No newline at end of file
diff --git a/content/agent/first-things-first/kerberos-agent-overview.gif b/content/agent/first-things-first/kerberos-agent-overview.gif
new file mode 100644
index 0000000..919d0de
Binary files /dev/null and b/content/agent/first-things-first/kerberos-agent-overview.gif differ
diff --git a/content/agent/installation/index.md b/content/agent/installation/index.md
new file mode 100644
index 0000000..6feff8e
--- /dev/null
+++ b/content/agent/installation/index.md
@@ -0,0 +1,50 @@
+---
+title: "Installation"
+description: "Install a Kerberos Agent where and how you want."
+lead: "Install a Kerberos Agent where and how you want."
+date: 2020-10-06T08:49:31+00:00
+lastmod: 2020-10-06T08:49:31+00:00
+draft: false
+images: []
+menu:
+ agent:
+ parent: "agent"
+weight: 202
+toc: true
+---
+
+The easiest to get your Kerberos Agent up and running is to use our Docker image on Docker hub. Once you selected a specific tag, run below command, which will open the web interface of your Kerberos agent on port 80. For persisting your configuration and/or recordings attach a volume. For more in depth configuration and installation verify [the Kerberos Agent repo](https://github.com/kerberos-io/agent).
+
+### Running as a container
+
+We are creating Docker images as part of our CI/CD process. You'll find our Docker images on [Docker hub](https://hub.docker.com/r/kerberos/agent). Pick a specific tag of choice, or use latest. Once done run below command, this will open the web interface of your Kerberos agent on port 80.
+
+ docker run -p 80:80 --name mycamera -d kerberos/agent:latest
+
+Or for a develop build:
+
+ docker run -p 80:80 --name mycamera -d kerberos/agent-dev:latest
+
+Feel free to use another port if your host system already has a workload running on `80`. For example `81`.
+
+ docker run -p 81:80 --name mycamera -d kerberos/agent-dev:latest
+
+### Attach a volume
+
+By default your Kerberos agent will store all its configuration and recordings inside the container. It might be interesting to store both configuration and your recordings outside the container, on your local disk. This helps persisting your storage even after you decide to wipe out your Kerberos agent.
+
+You attach a volume to your container by leveraging the `-v` option. To mount your own configuration file, execute as following:
+
+1. Decide where you would like to store your configuration and recordings; create a new directory for the config file and recordings folder accordingly.
+
+ mkdir agent
+ mkdir agent/config
+ mkdir agent/recordings
+
+2. Once you have located your desired directory, copy the latest [`config.json`](https://github.com/kerberos-io/agent/blob/master/machinery/data/config/config.json) file into your config directory.
+
+ wget https://raw.githubusercontent.com/kerberos-io/agent/master/machinery/data/config/config.json -O agent/config/config.json
+
+3. Run the docker command as following to attach your config directory and recording directory.
+
+ docker run -p 80:80 --name mycamera -v $(pwd)/agent/config:/home/agent/data/config -v $(pwd)/agent/recordings:/home/agent/data/recordings -d kerberos/agent:latest
diff --git a/content/factory/installation-cloud/index.md b/content/factory/installation-cloud/index.md
index 29ec82d..f33070b 100644
--- a/content/factory/installation-cloud/index.md
+++ b/content/factory/installation-cloud/index.md
@@ -4,7 +4,7 @@ description: ""
lead: ""
date: 2020-10-06T08:49:31+00:00
lastmod: 2020-10-06T08:49:31+00:00
-draft: false
+draft: true
images: []
menu:
factory:
diff --git a/content/factory/installation-edge/index.md b/content/factory/installation-edge/index.md
index 46dc33f..9185bff 100644
--- a/content/factory/installation-edge/index.md
+++ b/content/factory/installation-edge/index.md
@@ -4,7 +4,7 @@ description: ""
lead: ""
date: 2020-10-06T08:49:31+00:00
lastmod: 2020-10-06T08:49:31+00:00
-draft: false
+draft: true
images: []
menu:
factory:
diff --git a/content/factory/installation/index.md b/content/factory/installation/index.md
index 707093d..a4c2ea8 100644
--- a/content/factory/installation/index.md
+++ b/content/factory/installation/index.md
@@ -13,28 +13,28 @@ weight: 302
toc: true
---
-Kerberos Factory is shipped as a Docker container and is preferably installed inside a Kubernetes cluster. This means that it can run at the edge, or in the cloud.
+Kerberos Factory is shipped as a container image and is required to be installed inside a Kubernetes cluster. Kerberos Factory integrates with the Kubernetes API server to automatically provision Kerberos Agents on its behalf. This means that Kerberos Factory is out-of-scope if you are planning to use a `docker` or `docker compose` setup.
-Although you might except that Kubernetes at the edge or Kubernetes in the cloud is the same installation, you will notice that there are a few differences.
+You can run Kerberos Factory wherever you can run a Kubernetes cluster, so it can run at the edge, or in the cloud. Although you might except that Kubernetes at the edge or Kubernetes in the cloud is the same installation, you will notice that there are a few differences.
-When running a Kubernetes cluster on a Kubernetes service provider, such as [GKE](https://cloud.google.com/kubernetes-engine), [EKS](https://aws.amazon.com/eks/), you will have a couple of superpowers such as a `LoadBalancer` service, automatic `Volume` creation, etc. The latter is something what is missing in an Edge deployment, there you have to prepare the volumes yourself and install an edge load balancer like `MetalLB`.
+When running a managed Kubernetes cluster, such as [GKE](https://cloud.google.com/kubernetes-engine), [EKS](https://aws.amazon.com/eks/) or or [AKS](https://azure.microsoft.com/en-us/products/kubernetes-service/), you will have a wide range of superpowers such as a `LoadBalancer` service, automatic `Volume` creation, etc. The latter is something what is missing in an self-hosted deployment, where you will have to prepare the volumes yourself and install an edge load balancer like `MetalLB`.
{{< figure src="factory-edge-cloud.svg" alt="Kerberos Factory can be installed everywhere your Kubernetes cluster can be installed." caption="Kerberos Factory can be installed everywhere your Kubernetes cluster can be installed." class="stretch">}}
-## Installation on a Kubernetes Service Provider
+## Managed Kubernetes
-Installing Kerberos Factory on a Kubernetes Service Provider (Azure, GCP, AWS) is straight forward, as you can create a Kubernetes cluster in a few clicks, get access to public load balancers, volumes and more. Running Kerberos Vault in such a cluster is just a matter of copy-pasting some configuration (yaml) files, and execution of `kubectl apply` commands.
+Installing Kerberos Factory in a managed Kubernetes cluster (Azure, GCP, AWS) is straight forward, as you create Kubernetes clusters in a few clicks, get access to public load balancers, volumes and more. Running Kerberos Factory in a managed Kubernetes cluster is just a matter of copy-pasting some configuration (yaml) files, and execution of `kubectl apply` commands.
-Install Kerberos Vault on a Kubernetes Service Provider by [following this step-by-step installation guide](/factory/installation-cloud).
+Install Kerberos Factory in a managed Kubernetes cluster by [following this step-by-step installation guide](https://github.com/kerberos-io/factory/tree/master/kubernetes#b-managed-kubernetes-1).
-{{< figure src="factory-cloud.svg" alt="Process your video streams in the cloud." caption="Process your video streams in the cloud" class="stretch">}}
+{{< figure src="factory-cloud.svg" alt="Kerberos Factory managed cluster" caption="Kerberos Factory managed cluster" class="stretch">}}
-## Installation in a private cloud or at the edge
+## Self-hosted Kubernetes
No need to install Kerberos Factory on a Kubernetes Service Provider, it can be installed on your own Kubernetes cluster in your private cloud, or at the edge. The closer you bring Kerberos Vault to your video streams, and Kerberos Agents, the more benefits you will experience (low latency, low bandwidth, etc).
In contradiction to the Kubernetes Service Provider, there will be more work required. Setting up a Kubernetes Cluster, configure a load balancer, create persistent bolumes and claims.
-Install Kerberos Factory on a private cloud or at the edge by [following this step-by-step installation guide](/factory/installation-edge).
+Install Kerberos Factory on a private cloud or at the edge by [following this step-by-step installation guide](https://github.com/kerberos-io/factory/tree/master/kubernetes#a-self-hosted-kubernetes-1).
-{{< figure src="factory-edge.svg" alt="Process your video streams at the edge. " caption="Process your video streams at the edge." class="stretch">}}
+{{< figure src="factory-edge.svg" alt="Kerberos Factory self-hosted cluster" caption="Kerberos Factory self-hosted cluster" class="stretch">}}
diff --git a/content/opensource/first-things-first/index.md b/content/opensource/first-things-first/index.md
index e543384..597d0e5 100644
--- a/content/opensource/first-things-first/index.md
+++ b/content/opensource/first-things-first/index.md
@@ -13,6 +13,8 @@ weight: 201
toc: true
---
+***Kerberos Open Source is deprecated, please [use Kerberos Agent](/agent/first-things-first) instead.***
+
Kerberos started as an Open Source project back in 2014. Our main goal was, and still is, to provide everyone in this world with a free, professional and complete video surveillance system, which they can install in a couple of minutes.
Kerberos was initially developed for the Raspberry Pi, due to this many of the tools we have been using are lightweight and fast (such as C++). Over the years we have found other ways to make Kerberos available, such as KiOS (our custom Linux), Docker and Kubernetes.
diff --git a/content/prologue/deployments/index.md b/content/prologue/deployments/index.md
index d548da4..0ba8f51 100644
--- a/content/prologue/deployments/index.md
+++ b/content/prologue/deployments/index.md
@@ -27,7 +27,7 @@ The most common scenario is to install your Kerberos Agents at the edge. This ha
### Less than 5 cameras streams
-When having limited number of cameras streams, and there is no need for any high availability or scaling, then multiple individual Kerberos Agents are a good choice. For example, you can install the Kerberos Agent on a Raspberry Pi, by using [KiOS](/opensource/installation#kios), [Raspbian OS](/opensource/installation-advanced#raspbian) or compile it from source.
+When having limited number of cameras streams, and there is no need for any high availability or scaling, then multiple individual Kerberos Agents are a good choice. For example, you can install the [Kerberos Agent](/agent/first-things-first) on a Raspberry Pi, a VM or install it from source.
On below architecture, a couple of Kerberos Agents are installed at the edge (inside the local network). A Kerberos Agent is installed for each camera stream, and each Kerberos Agent runs on a separate host (Raspberry Pi, VM, etc). The front-end of the Kerberos Agents can be reached from the internal network, but cannot be accessed from the internet.
@@ -37,12 +37,12 @@ Another option to install the Kerberos Agent is to use Docker. Instead of having
Running your Kerberos Agents inside Docker containers, allows you to process multiple surveillance cameras using only one host.
-{{< figure src="kerberos-agent-docker.svg" alt="Having just a few of cameras to be monitored then Kerberos Agent on 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">}}
+{{< figure src="kerberos-agent-docker.svg" alt="Having just a few of cameras to be monitored then Kerberos Agent on Docker might be the right choice." caption="Having just a few of cameras to be monitored then Kerberos Agent with Docker might be the right choice." class="stretch">}}
### More than 5 camera streams
Having more camera streams and Kerberos Agents will become a bit tedious to manage, and you might start looking for other solutions in terms of scaling and also storage.
-When having more than 5 [Kerberos Agents](/opensource/first-things-first/), the Kerberos Enterprise Suite starts to become interesting. While building on Kubernetes, your Kerberos Agents will be scheduled and deployed more easily through [Kerberos Factory](/factory/first-things-first/). Your recordings will be stored centrally using [Kerberos Vault](/vault/first-things-first/), and you will be able to review everything from within a single pane of glass with [Kerberos Hub](/hub/first-things-first/).
+When having more than 5 [Kerberos Agents](/agent/first-things-first/), the Kerberos Enterprise Suite starts to become interesting. While building on Kubernetes, your Kerberos Agents will be scheduled and deployed more easily through [Kerberos Factory](/factory/first-things-first/). Your recordings will be stored centrally using [Kerberos Vault](/vault/first-things-first/), and you will be able to review everything from within a single pane of glass with [Kerberos Hub](/hub/first-things-first/).
{{< figure src="kerberos-enterprise-suite.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">}}
diff --git a/content/prologue/how/index.md b/content/prologue/how/index.md
index 1cc369b..9bbefe8 100644
--- a/content/prologue/how/index.md
+++ b/content/prologue/how/index.md
@@ -13,21 +13,21 @@ weight: 102
toc: true
---
-A [Kerberos Agent](/opensource/first-things-first/), is a piece of software that is responsible for monitoring a single camera stream. It contains two pieces: a front-end and a back-end. The back-end processes the video stream, applies computer vision techniques, makes recordings and takes actions (for example sending notifications). The front-end allows you to review recordings, and configure specific settings for the back-end.
+A [Kerberos Agent](/agent/first-things-first/), is a piece of software that is responsible for monitoring a single camera stream. It contains two pieces: a front-end and a back-end. The back-end processes the video stream, applies computer vision techniques, makes recordings and takes actions (for example sending notifications). The front-end allows you to review recordings, and configure specific settings for 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">}}
## Kerberos Vault
-End-consumer or enterprises which only have a few camera streams to manage, probably will be fine with just one or more [Kerberos Agents](/opensource/first-things-first/). If remote access is required they could also benefit from the [Kerberos Hub Saas offering](/hub/first-things-first).
+End-consumer or enterprises which only have a few camera streams to manage, probably will be fine with just one or more [Kerberos Agents](/agent/first-things-first/). If remote access is required they could also benefit from the [Kerberos Hub Saas offering](/hub/first-things-first).
-As soon you will process more [Kerberos Agents](/opensource/first-things-first/), it will become interesting to manage your own central storage through [Kerberos Vault](/vault/first-things-first/). If you want to bring your own integrations or machine learning models than [Kerberos Vault](/vault/first-things-first/) is also the way forward.
+As soon you will process more [Kerberos Agents](/agent/first-things-first/), it will become interesting to manage your own central storage through [Kerberos Vault](/vault/first-things-first/). If you want to bring your own integrations or machine learning models than [Kerberos Vault](/vault/first-things-first/) is also the way forward.
{{< figure src="vault-edge-cloud-storage.svg" alt="Bring your own storage using Vault" caption="Bring your own storage using Kerberos Vault" class="stretch">}}
## Kerberos Hub
-One or more [Kerberos Agents](/opensource/first-things-first/) are perfect for a small scale deployment. The disadvantage, when running a couple of Kerberos Agents, is that an agent is designed to handle a single camera stream. This means if you would like to have an overview of all your [Kerberos Agents](/opensource/first-things-first/), you will need to open multiple interfaces or build something yourself. Another disadvantage is the network, typically a Kerberos Agent is on a local network, and not accessible from the internet. This requires port-forwarding, or a VPN tunnel to properly secure and access them.
+One or more [Kerberos Agents](/agent/first-things-first/) are perfect for a small scale deployment. The disadvantage, when running a couple of Kerberos Agents, is that an agent is designed to handle a single camera stream. This means if you would like to have an overview of all your [Kerberos Agents](/agent/first-things-first/), you will need to open multiple interfaces or build something yourself. Another disadvantage is the network, typically a Kerberos Agent is on a local network, and not accessible from the internet. This requires port-forwarding, or a VPN tunnel to properly secure and access them.
{{< figure src="hub-with-vault.svg" alt="Kerberos Vault connected to Kerberos Hub." caption="Kerberos Vault connected to Kerberos Hub." class="stretch">}}
diff --git a/content/vault/configuration/index.md b/content/vault/configuration/index.md
index 8c40cc8..2296547 100644
--- a/content/vault/configuration/index.md
+++ b/content/vault/configuration/index.md
@@ -21,8 +21,6 @@ The steps we have to go through to get a functional Kerberos Vault are as follow
2. implement and configure one or more integrations,
3. create an account, so Kerberos Vault can be consumed.
--- TODO show an image illustrating what has to be done.
-
## 1. Providers
Storage providers are the foundation of Kerberos Vault. As an administrator you bring your own cloud or edge storage, so there is no need to install a specific Kerberos Vault storage, we are open and integrate with others.
diff --git a/content/vault/installation-cloud/index.md b/content/vault/installation-cloud/index.md
index 66bbbac..786cfab 100644
--- a/content/vault/installation-cloud/index.md
+++ b/content/vault/installation-cloud/index.md
@@ -4,7 +4,7 @@ description: ""
lead: ""
date: 2020-10-06T08:49:31+00:00
lastmod: 2020-10-06T08:49:31+00:00
-draft: false
+draft: true
images: []
menu:
vault:
diff --git a/content/vault/installation-edge/index.md b/content/vault/installation-edge/index.md
index ee4f9d0..4d85abe 100644
--- a/content/vault/installation-edge/index.md
+++ b/content/vault/installation-edge/index.md
@@ -4,7 +4,7 @@ description: ""
lead: ""
date: 2020-10-06T08:49:31+00:00
lastmod: 2020-10-06T08:49:31+00:00
-draft: false
+draft: true
images: []
menu:
vault:
diff --git a/content/vault/installation/index.md b/content/vault/installation/index.md
index 369aaf4..ff6772d 100644
--- a/content/vault/installation/index.md
+++ b/content/vault/installation/index.md
@@ -13,28 +13,36 @@ weight: 302
toc: true
---
-Kerberos Vault is shipped as a Docker container and is preferably installed inside a Kubernetes cluster. This means that it can run at the edge, or in the cloud.
+Kerberos Vault is shipped as a container image and is preferably installed inside a Kubernetes cluster. This means that you can run it where and how you want. Depending on your setup, home installation or production ready deployment, you might decide to install it using standard `Docker` or `Kubernetes` depending on your needs and requirements.
-Although you might expect that Kubernetes at the edge or Kubernetes in the cloud is the same installation, you will notice that there are a few differences.
+## Docker
-When running a Kubernetes cluster on a Kubernetes service provider, such as [GKE](https://cloud.google.com/kubernetes-engine), [EKS](https://aws.amazon.com/eks/), you will have a couple of superpowers such as a `LoadBalancer` service, automatic `Volume` creation, etc. The latter is something what is missing in an Edge deployment, there you have to prepare the volumes yourself and install an edge load balancer like `MetalLB`.
+You can quickly ramp-up Kerberos Vault by using `docker compose`. We have provided a `docker-compose.yaml` file, which includes all the required services.
+
+> Install Kerberos Vault using `docker compose` [following this step-by-step installation guide](https://github.com/kerberos-io/vault/tree/master/docker).
+
+## Kubernetes
+
+Although you might expect that self-hosted Kubernetes or a managed Kubernetes in the cloud is the same, you will notice that there are a few differences in terms of installation.
+
+When running a Kubernetes cluster on a Kubernetes service provider, such as [GKE](https://cloud.google.com/kubernetes-engine), [EKS](https://aws.amazon.com/eks/) or [AKS](https://azure.microsoft.com/en-us/products/kubernetes-service/) you will have a wide range of superpowers such as a `LoadBalancer` service, automatic `Volume` creation, etc. The latter is something what is missing in an Edge deployment, there you have to prepare the volumes yourself and install an edge load balancer like `MetalLB`.
{{< figure src="vault-edge-cloud-deployments.svg" alt="Kerberos Vault can be installed everywhere your Kubernetes cluster can be installed." caption="Kerberos Vault can be installed everywhere your Kubernetes cluster can be installed." class="stretch">}}
-## Installation on a Kubernetes Service Provider
+## Managed Kubernetes
Installing Kerberos Vault on a Kubernetes Service Provider (Azure, GCP, AWS) is straight forward, as you can create a Kubernetes cluster in a few clicks, get access to public load balancers, volumes and more. Running Kerberos Vault in such a cluster is just a matter of copy-pasting some configuration (yaml) files, and execution of `kubectl apply` commands.
-Install Kerberos Vault on a Kubernetes Service Provider by [following this step-by-step installation guide](/vault/installation-cloud).
+> Install Kerberos Vault on a Kubernetes Service Provider by [following this step-by-step installation guide](https://github.com/kerberos-io/vault/tree/master/kubernetes#a-managed-kubernetes-1).
{{< figure src="vault-cloud-deployment.svg" alt="Bring your own storage using Kerberos Vault" caption="Bring your own storage using Kerberos Vault" class="stretch">}}
-## Installation in a private cloud or at the edge
+## Self-hosted Kubernetes
No need to install Kerberos Vault on a Kubernetes Service Provider, it can be installed on your own Kubernetes cluster in your private cloud, or at the edge. The closer you bring Kerberos Vault to your video streams, and Kerberos Agents, the more benefits you will experience (low latency, low bandwidth, etc).
In contrast to the Kubernetes Service Provider, there will be more work required. Setting up a Kubernetes Cluster, configuring a load balancer, and creating persistent volumes and claims.
-Install Kerberos Vault on a private cloud or at the edge by [following this step-by-step installation guide](/vault/installation-edge).
+> Install Kerberos Vault on a private cloud or at the edge by [following this step-by-step installation guide](https://github.com/kerberos-io/vault/tree/master/kubernetes#b-self-hosted-kubernetes-1).
{{< figure src="vault-edge-deployment.svg" alt="Store your recordings at the edge with Kerberos Vault" caption="Store your recordings at the edge with Kerberos Vault" class="stretch">}}
diff --git a/content/vault/installation/old/deployment-models.svg b/content/vault/installation/old/deployment-models.svg
deleted file mode 100644
index e13e2f1..0000000
--- a/content/vault/installation/old/deployment-models.svg
+++ /dev/null
@@ -1,415 +0,0 @@
-
diff --git a/content/vault/installation/old/deployments-models.svg b/content/vault/installation/old/deployments-models.svg
deleted file mode 100644
index 9c4129a..0000000
--- a/content/vault/installation/old/deployments-models.svg
+++ /dev/null
@@ -1,224 +0,0 @@
-
diff --git a/layouts/partials/sidebar/docs-menu.html b/layouts/partials/sidebar/docs-menu.html
index cd1ca0f..605a0e6 100644
--- a/layouts/partials/sidebar/docs-menu.html
+++ b/layouts/partials/sidebar/docs-menu.html
@@ -10,17 +10,6 @@
{{ end -}}
{{ end -}}
-{{ range .Site.Menus.opensource -}}
-
{{ .Name }}
- {{ if .HasChildren -}}
-
- {{ range .Children -}}
- {{- $active := or ($currentPage.IsMenuCurrent "opensource" .) ($currentPage.HasMenuCurrent "opensource" .) -}}
-