Update ingress.md API version

Signed-off-by: Salim Adedeji <adedejisalim@yahoo.com>
cert-manager · Mar 15, 2021 · 59df694 · 59df694
1 parent 53c4910
commit 59df694
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/content/en/docs/usage/ingress.md b/content/en/docs/usage/ingress.md
@@ -20,7 +20,7 @@ resource with the name provided in the `tls.secretName` field and configured as
 described on the `Ingress` exists. For example:
 
 ```yaml
-apiVersion: extensions/v1beta1
+apiVersion: networking.k8s.io/v1
 kind: Ingress
 metadata:
   annotations:
@@ -120,4 +120,4 @@ guide](../../installation/).
 
 ## Troubleshooting
 
-If you do not see a `Certificate` resource being created after applying the ingress-shim annotations check that at least `cert-manager.io/issuer` or `cert-manager.io/cluster-issuer` is set. If you want to use `kubernetes.io/tls-acme: "true"` make sure to have checked all steps above and you might want to look for errors in the cert-manager pod logs if not resolved.
+If you do not see a `Certificate` resource being created after applying the ingress-shim annotations check that at least `cert-manager.io/issuer` or `cert-manager.io/cluster-issuer` is set. If you want to use `kubernetes.io/tls-acme: "true"` make sure to have checked all steps above and you might want to look for errors in the cert-manager pod logs if not resolved.