From f41244e54966537b11058213ef31bb9ff897ba53 Mon Sep 17 00:00:00 2001
From: Sander Rodenhuis <sander.rodenhuis@redkubes.com>
Date: Tue, 7 Nov 2023 10:41:17 +0100
Subject: [PATCH] fix: cf token

---
 docs/get-started/installation/byo-wildcard.md | 27 +++++++++++++++++--
 docs/get-started/installation/entrypoint.md   |  4 ++-
 docs/get-started/overview.md                  |  3 +++
 3 files changed, 31 insertions(+), 3 deletions(-)

diff --git a/docs/get-started/installation/byo-wildcard.md b/docs/get-started/installation/byo-wildcard.md
index d1475af07..418cbffb3 100644
--- a/docs/get-started/installation/byo-wildcard.md
+++ b/docs/get-started/installation/byo-wildcard.md
@@ -9,10 +9,33 @@ When installing Otomi with DNS, there are 3 `issuers` you can use:
 2. letsencrypt
 3. byo-wildcard-cert
 
-In the installation examples we use `letsencrypt`. In this example we'll show how to use a Bring Your Own wildcard certificate.
+In most of the installation examples we use `letsencrypt`. In this example we'll show how to use a Bring Your Own wildcard certificate.
 
 To use a `byo-wildcard-cert`, install otomi with the following values:
 
 ```yaml
-
+cluster:
+  name: otomi
+  provider: aws # adjust to your provider
+  domainSuffix: try-otomi.net
+otomi:
+  hasExternalDNS: true
+dns:
+  domainFilters: 
+    - try-otomi.net
+  provider:
+    aws:
+      credentials:
+        secretKey: xxx
+        accessKey: xxx
+      region: eu-central-1
+apps:
+  cert-manager:
+    issuer: byo-wildcard-cert
+    byoWildcardCert: |
+      -----BEGIN CERTIFICATE-----
+      -----END CERTIFICATE-----
+    byoWildcardCertKey: |
+      -----BEGIN PRIVATE KEY-----
+      -----END PRIVATE KEY-----
 ```
\ No newline at end of file
diff --git a/docs/get-started/installation/entrypoint.md b/docs/get-started/installation/entrypoint.md
index c71ad9498..9df8e80b4 100644
--- a/docs/get-started/installation/entrypoint.md
+++ b/docs/get-started/installation/entrypoint.md
@@ -20,4 +20,6 @@ ingress:
     entrypoint: <entrypoint-ip-address>
 ```
 
-Make sure the external gateway is able to connect to the IP of the private load balancer used by the `platformClass` ingress controller.
\ No newline at end of file
+Make sure the external gateway is configured to connect to the IP of the private load balancer used by the `platformClass` ingress controller.
+
+The DNS A records created by Otomi will now all point to the IP address of the external gateway.
\ No newline at end of file
diff --git a/docs/get-started/overview.md b/docs/get-started/overview.md
index 5568cd915..80f6f959c 100644
--- a/docs/get-started/overview.md
+++ b/docs/get-started/overview.md
@@ -61,4 +61,7 @@ Install Otomi with KMS
 ### [Configure an entrypoint for an external gateway](installation/entrypoint.md)
 Install Otomi with an entrypoint for an external gateway
 
+### [Bring Your Own Wild Card Certificate](installation/byo-wildcard.md)
+Install Otomi using a BYO wild card certificate
+
 ---