Add docs for new Ingress annotation "acme.cert-manager.io/http01-override-ingress-ingressclassname"

Signed-off-by: Yuedong Wu <[email protected]>

Author: lunarwhite

.spelling

@@ -853,6 +853,7 @@ example.org
 experimental.cert
 http01-edit-in-place
 http01-ingress-class
+http01-ingress-ingressclassname
 ingress.class
 ip-sans
 kubernetes.io

content/docs/configuration/acme/http01/README.md

@@ -69,6 +69,9 @@ controllers support `ingressClassName`, with the notable exception of
 ingress-gce (as per the page [Configure Ingress for external load
 balancing](https://cloud.google.com/kubernetes-engine/docs/how-to/load-balance-ingress)).
 
+> You can override the `ingressClassName` on a per-Ingress basis using the
+[`acme.cert-manager.io/http01-ingress-ingressclassname`](https://cert-manager.io/docs/reference/annotations/#acmecert-manageriohttp01-ingress-ingressclassname) annotation.
+
 ### `class`
 
 If the `class` field is specified, a new Ingress resource with a randomly
@@ -79,6 +82,9 @@ value set to the value of the `class` field.
 This field is only recommended with ingress-gce. ingress-gce [doesn't support the
 `ingressClassName` field](https://cloud.google.com/kubernetes-engine/docs/how-to/load-balance-ingress).
 
+> You can override the `class` on a per-Ingress basis using the
+[`acme.cert-manager.io/http01-ingress-class`](https://cert-manager.io/docs/reference/annotations/#acmecert-manageriohttp01-ingress-class) annotation.
+
 ### `name`
 
 If the `name` field is specified, cert-manager will edit the named

content/docs/reference/annotations.md

@@ -27,12 +27,20 @@ This is useful for keeping compatibility with the `ingress-gce` component.
 ## acme.cert-manager.io/http01-ingress-class
 - [Ingress](../usage/ingress.md)
 
-this annotation allows you to configure the ingress class that will be used to
-solve challenges for this ingress. Customizing this is useful when you are
-trying to secure internal services, and need to solve challenges using a
-different ingress class to that of the ingress. If not specified and the
-`acme-http01-edit-in-place` annotation is not set, this defaults to the ingress
-class defined in the Issuer resource.
+this annotation allows you to configure the `kubernetes.io/ingress.class` that will be
+used to solve challenges for this ingress. Customizing this is useful when you are trying
+to secure internal services, and need to solve challenges using a different ingress class
+to that of the ingress. If not specified and the `acme-http01-edit-in-place` annotation is
+not set, this defaults to the `http01.ingress.class` defined in the Issuer resource.
+
+## acme.cert-manager.io/http01-ingress-ingressclassname
+- [Ingress](../usage/ingress.md)
+
+this annotation allows you to configure the `spec.ingressClassName` that will be
+used to solve challenges for this ingress. Customizing this is useful when you are trying
+to secure internal services, and need to solve challenges using a different ingress class
+to that of the ingress. If not specified and the `acme-http01-edit-in-place` annotation is
+not set, this defaults to the `http01.ingress.ingressClassName` defined in the Issuer resource.
 
 ## cert-manager.io/allow-direct-injection
 - `Secret`

content/docs/usage/ingress.md

@@ -3,7 +3,7 @@ title: Annotated Ingress resource
 description: 'cert-manager usage: Kubernetes Ingress'
 ---
 
-> **apiVersion:** networking.k8s.io/v1  
+> **apiVersion:** networking.k8s.io/v1
 > **kind:** Ingress
 
 <div style={{textAlign: "center"}}>
@@ -89,11 +89,19 @@ trigger `Certificate` resources to be automatically created:
   container.
 
 - `acme.cert-manager.io/http01-ingress-class`: this annotation allows you to
-  configure the ingress class that will be used to solve challenges for this
-  ingress. Customizing this is useful when you are trying to secure internal
+  configure the `kubernetes.io/ingress.class` that will be used to solve challenges
+  for this ingress. Customizing this is useful when you are trying to secure internal
   services, and need to solve challenges using a different ingress class to that
   of the ingress. If not specified and the `acme-http01-edit-in-place` annotation
-  is not set, this defaults to the ingress class defined in the Issuer resource.
+  is not set, this defaults to the `http01.ingress.class` defined in the Issuer resource.
+
+- `acme.cert-manager.io/http01-ingress-ingressclassname`: this annotation allows you to
+  configure the `spec.ingressClassName` that will be used to solve challenges
+  for this ingress. Customizing this is useful when you are trying to secure internal
+  services, and need to solve challenges using a different ingress class to that
+  of the ingress. If not specified and the `acme-http01-edit-in-place` annotation
+  is not set, this defaults to the `http01.ingress.ingressClassName` defined in the
+  Issuer resource.
 
 - `acme.cert-manager.io/http01-edit-in-place: "true"`: this controls whether the
   ingress is modified 'in-place', or a new one is created specifically for the