From f6af3b460a262bc75278ea17e15f2c16ac69b7f3 Mon Sep 17 00:00:00 2001
From: Gabriel Gosselin <12598930+toutougabi@users.noreply.github.com>
Date: Mon, 14 Nov 2022 21:58:41 -0500
Subject: [PATCH] Missing controller.ingressClass (#9304)

The missing controller.ingressClass would set the deployment to the default class but the controller.ingressClassResource.name would set the creation of a new IngressClass object.

For now this needs to be done twice, could be a fix in the chart later on.
---
 docs/index.md | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/docs/index.md b/docs/index.md
index 5687bf5d3..fded1b2bc 100644
--- a/docs/index.md
+++ b/docs/index.md
@@ -223,6 +223,7 @@ If you start Ingress-Nginx B with the command line argument `--watch-ingress-wit
   helm install ingress-nginx-2 ingress-nginx/ingress-nginx  \
   --namespace ingress-nginx-2 \
   --set controller.ingressClassResource.name=nginx-two \
+  --set controller.ingressClass=nginx-two \
   --set controller.ingressClassResource.controllerValue="example.com/ingress-nginx-2" \
   --set controller.ingressClassResource.enabled=true \
   --set controller.ingressClassByName=true
@@ -234,7 +235,9 @@ If you start Ingress-Nginx B with the command line argument `--watch-ingress-wit
   --namespace kube-system \
   --set controller.electionID=nginx-two-leader \
   --set controller.ingressClassResource.name=nginx-two \
+  --set controller.ingressClass=nginx-two \
   --set controller.ingressClassResource.controllerValue="example.com/ingress-nginx-2" \
   --set controller.ingressClassResource.enabled=true \
   --set controller.ingressClassByName=true
-  ```
\ No newline at end of file
+  ```
+  - Note, controller.ingressClassResource.name and controller.ingressClass have to be set with the value of the new class as the first is to create the IngressClass object and the other is to modify the deployment of the actuall ingress controller pod.