update images enterprise agent

content/enterprise/installation-cloud/index.md

@@ -175,4 +175,4 @@ It should look like this.
 
 Once everything is configured correctly your cluster and DNS, you should be able to setup the Factory application. By navigating to the Factory domain `factory.domain.com` in your browser you will see the Factory login page showing up.
 
-<img src="/images/factory/kerberos-factory-loginpage.png" style="width: 100%"/>
+{{< figure src="login.png" alt="Once successfully installed Kerberos Enterprise, it will show you the login page." caption="Once successfully installed Kerberos Enterprise, it will show you the login page." class="stretch">}}

content/enterprise/installation-edge/index.md

@@ -15,7 +15,7 @@ toc: true
 
 Welcome to the Kerberos Enterprise Edge installation. This is the way to go if you want to install Kerberos Enterprise on your Baremetal infrastructure or inside your Private Cloud.
 
-<img src="/images/prologue/deployments/onpremise-more-then-5.svg" style="width: 100%"/>
+{{< figure src="../../prologue/deployments/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">}}
 
 Before we can actual start installing the different deployments in our cluster, we need to make sure we have one available.
 
@@ -254,4 +254,4 @@ It should look like this.
 
 Once everything is configured correctly your cluster and DNS, you should be able to setup the Factory application. By navigating to the Factory domain `factory.domain.com` in your browser you will see the Factory login page showing up.
 
-<img src="/images/factory/kerberos-factory-loginpage.png" style="width: 100%"/>
+{{< figure src="login.png" alt="Once successfully installed Kerberos Enterprise, it will show you the login page." caption="Once successfully installed Kerberos Enterprise, it will show you the login page." class="stretch">}}

content/enterprise/installation/index.md

@@ -17,7 +17,7 @@ Kerberos Enterprise can be installed where Kubernetes can be installed. This mea
 
 Although you might except Kubernetes at the Edge or Kubernetes in the cloud, there are no differences, well sorry to say there are. As Kubernetes service providers implemented features such as LoadBalancers, Persistent Volumes, and others, they have automated and integrated a huge portion of the Kubernetes stack with their related PAAS services. To be more concrete if you are running a Kubernetes Cluster on GCP, you will use the LoadBalancing and Storage services from GCP.
 
-<img src="/images/factory/kerberos-enterprise-kubernetes.png" style="width: 100%"/><br/>
+{{< figure src="deployment-models.svg" alt="Kerberos Enterprise can be installed everywhere your Kubernetes cluster can be installed." caption="Kerberos Enterprise can be installed everywhere your Kubernetes cluster can be installed." class="stretch">}}
 
 Compared to Kubernetes at the Edge, there are no predefined LoadBalancers, Storage capabilities, and more. This means more administration work for you, but - with great power comes great responsibility - so no worries. In the end there are alternative functionalties available, for features which you find out-of-the-box at the Kubernetes service providers, you just have to spend more time on configuring and installing those services/pods/deployments yourself.
 
@@ -25,7 +25,7 @@ Compared to Kubernetes at the Edge, there are no predefined LoadBalancers, Stora
 
 Installing Kerberos Enterprise 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, storage and more. Running Kerberos Enterprise in such a cluster is just a matter of copy-pasting some configuration (yaml) files, and executing some `kubectl apply` commands.
 
-<img src="/images/prologue/deployments/cloud-more-then-5.svg" style="width: 100%"/>
+{{< figure src="../../prologue/deployments/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">}}
 
 Install Kerberos Enterprise on a Kubernetes Service Provider by [following this step-by-step installation guide](/enterprise/installation-cloud).
 
@@ -33,7 +33,7 @@ Install Kerberos Enterprise on a Kubernetes Service Provider by [following this
 
 No need to install Kerberos Enterprise on a Kubernetes Service Provider, you could install it on your own Kubernetes cluster in your private cloud, or even better inside your own premise. The closer you bring Kerberos Enterprise to your surveillance infrastructure, the more benefits you will experience (low latency, low bandwidth, etc).
 
-<img src="/images/prologue/deployments/onpremise-more-then-5.svg" style="width: 100%"/>
+{{< figure src="../../prologue/deployments/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">}}
 
 In contradiction to the Kubernetes Service Provider, you will have some work todo. Setting up Kubernetes Cluster, play with MetalLB, Persistent Volumes and claims. Don't be scared, it's pretty ssttraight forward as well. You can't simple expect a: click, click, 💥 approach.
 

content/enterprise/releases/index.md

@@ -1,5 +1,5 @@
 ---
-title: "Releases2"
+title: "Releases"
 description: ""
 lead: ""
 date: 2020-10-06T08:49:31+00:00