From e21f0563f3d00c47b86c6e43619aaeeeb1c4cf25 Mon Sep 17 00:00:00 2001
From: Michelle Fernandez Bieber <37021266+mfbieber@users.noreply.github.com>
Date: Sun, 5 Dec 2021 01:55:29 +0100
Subject: [PATCH] Added ingressClassName: nginx to Ingress example, mentioned
 to the necessity of it and referenced to the section describing that further

---
 .../concepts/services-networking/ingress.md     | 17 +++++++++++++++++
 .../networking/default-ingressclass.yaml        | 10 ++++++++++
 .../service/networking/minimal-ingress.yaml     |  1 +
 3 files changed, 28 insertions(+)
 create mode 100644 content/en/examples/service/networking/default-ingressclass.yaml

diff --git a/content/en/docs/concepts/services-networking/ingress.md b/content/en/docs/concepts/services-networking/ingress.md
index 3e2aeb6773..882108fc8b 100644
--- a/content/en/docs/concepts/services-networking/ingress.md
+++ b/content/en/docs/concepts/services-networking/ingress.md
@@ -88,6 +88,15 @@ has all the information needed to configure a load balancer or proxy server. Mos
 contains a list of rules matched against all incoming requests. Ingress resource only supports rules
 for directing HTTP(S) traffic.
 
+If the `ingressClassName` is omitted, a [default Ingress class](#default-ingress-class) 
+should be defined.
+
+There are some ingress controllers, that work without the definition of a 
+default `IngressClass`. For example, the Ingress-NGINX controller can be 
+configured with a [flag](https://kubernetes.github.io/ingress-nginx/#what-is-the-flag-watch-ingress-without-class) 
+`--watch-ingress-without-class`. It is [recommended](https://kubernetes.github.io/ingress-nginx/#i-have-only-one-instance-of-the-ingresss-nginx-controller-in-my-cluster-what-should-i-do)  though, to specify the 
+default `IngressClass` as shown [below](#default-ingress-class).
+
 ### Ingress rules
 
 Each HTTP rule contains the following information:
@@ -266,6 +275,14 @@ an `ingressClassName` specified. You can resolve this by ensuring that at most 1
 IngressClass is marked as default in your cluster.
 {{< /caution >}}
 
+There are some ingress controllers, that work without the definition of a
+default `IngressClass`. For example, the Ingress-NGINX controller can be
+configured with a [flag](https://kubernetes.github.io/ingress-nginx/#what-is-the-flag-watch-ingress-without-class)
+`--watch-ingress-without-class`. It is [recommended](https://kubernetes.github.io/ingress-nginx/#i-have-only-one-instance-of-the-ingresss-nginx-controller-in-my-cluster-what-should-i-do)  though, to specify the
+default `IngressClass`:
+
+{{< codenew file="service/networking/default-ingressclass.yaml" >}}
+
 ## Types of Ingress
 
 ### Ingress backed by a single Service {#single-service-ingress}
diff --git a/content/en/examples/service/networking/default-ingressclass.yaml b/content/en/examples/service/networking/default-ingressclass.yaml
new file mode 100644
index 0000000000..0602ad8c9d
--- /dev/null
+++ b/content/en/examples/service/networking/default-ingressclass.yaml
@@ -0,0 +1,10 @@
+apiVersion: networking.k8s.io/v1
+kind: IngressClass
+metadata:
+  labels:
+    app.kubernetes.io/component: controller
+  name: nginx-example
+  annotations:
+    ingressclass.kubernetes.io/is-default-class: "true"
+spec:
+  controller: k8s.io/ingress-nginx
diff --git a/content/en/examples/service/networking/minimal-ingress.yaml b/content/en/examples/service/networking/minimal-ingress.yaml
index 76640b9447..55a5837510 100644
--- a/content/en/examples/service/networking/minimal-ingress.yaml
+++ b/content/en/examples/service/networking/minimal-ingress.yaml
@@ -5,6 +5,7 @@ metadata:
   annotations:
     nginx.ingress.kubernetes.io/rewrite-target: /
 spec:
+  ingressClassName: nginx-example
   rules:
   - http:
       paths: