From 560ba5dffc4bdfdb86b357a722c1bdfbb13b8d6f Mon Sep 17 00:00:00 2001 From: Olivier Karasangabo Date: Tue, 7 Nov 2023 14:51:03 +0100 Subject: [PATCH] =?UTF-8?q?=F0=9F=93=9D=20docs:=20Update=20kind=20cluster?= =?UTF-8?q?=20setup=20docs?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Deploying an NGINX ingress controller is required for `unguard.kube` (referenced in the "application deployment" step) to work. However, the docs make it seem like this step is optional. --- docs/DEV-GUIDE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/DEV-GUIDE.md b/docs/DEV-GUIDE.md index 6e7cc31d..4a13b9a9 100644 --- a/docs/DEV-GUIDE.md +++ b/docs/DEV-GUIDE.md @@ -26,7 +26,7 @@ This document explains how to build and run Unguard locally inside Kubernetes us kind create cluster --name unguard --config ./k8s-manifests/localdev/kind/cluster-config.yaml ``` - * Optionally add an nginx ingress controller if you want to expose Unguard locally without port-forwarding + * Also, make sure to deploy an nginx ingress controller so that Unguard can be exposed locally (without port-forwarding) ```sh kubectl apply -k ./k8s-manifests/localdev/kind/ ```