From ae8ad1fb937169f696e24932be0e935827f4284b Mon Sep 17 00:00:00 2001
From: Giuseppe Capizzi <gcapizzi@vmware.com>
Date: Wed, 19 Jul 2023 15:10:33 +0000
Subject: [PATCH] Improve INSTALL.kind.md

Co-authored-by: Georgi Sabev <georgethebeatle@gmail.com>
---
 INSTALL.kind.md | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/INSTALL.kind.md b/INSTALL.kind.md
index ec1c4d6f2..5943dad5b 100644
--- a/INSTALL.kind.md
+++ b/INSTALL.kind.md
@@ -23,7 +23,7 @@ BASE_DOMAIN="apps-127-0-0-1.nip.io"
 In order to access the Korifi API, we'll need to [expose the cluster ingress locally](https://kind.sigs.k8s.io/docs/user/ingress/). To do it, create your kind cluster using a command like this:
 
 ```sh
-cat <<EOF | kind create cluster --config=-
+cat <<EOF | kind create cluster --name korifi --config=-
 kind: Cluster
 apiVersion: kind.x-k8s.io/v1alpha4
 nodes:
@@ -57,7 +57,6 @@ Make sure you pass the following flags to the Metrics Server container (see [_Co
 
 No changes here, follow the [common instructions](./INSTALL.md#pre-install-configuration).
 For the container registry credentials `Secret`, we recommend you [create an access token](https://hub.docker.com/settings/security?generateToken=true) on DockerHub.
-Remember to set `global.generateIngressCertificates` to `true` if you want to use self-signed TLS certificates.
 
 ## Install Korifi
 
@@ -67,6 +66,8 @@ If using DockerHub as recommended above, set the following values:
 -   `kpackImageBuilder.builderRepository`: `index.docker.io/<username>/kpack-builder`;
 -   `global.containerRepositoryPrefix`: `index.docker.io/<username>/`;
 
+Remember to set `global.generateIngressCertificates` to `true` if you want to use self-signed TLS certificates.
+
 If `$KORIFI_NAMESPACE` doesn't exist yet, you can add the `--create-namespace` flag to the `helm` invocation.
 
 ## Post-install Configuration
@@ -76,4 +77,4 @@ Yon can skip this section.
 ## Test Korifi
 
 No changes here, follow the [common instructions](./INSTALL.md#test-korifi).
-When running `cf login`, make sure you select the entry associated to your kind cluster (`kind-kind` by default).
+When running `cf login`, make sure you select the entry associated to your kind cluster (`kind-korifi` in our case).