Skip to content

Commit 4572f2e

Browse files
authored
Merge pull request #125211 from poyajoon/patch-1
Update ingress-controller-letsencrypt-certificate-application-gateway.md
2 parents d327355 + f2b077f commit 4572f2e

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/application-gateway/ingress-controller-letsencrypt-certificate-application-gateway.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -139,7 +139,7 @@ Use the following steps to install [cert-manager](https://docs.cert-manager.io)
139139
140140
4. After you successfully set up your staging certificate, you can switch to a production ACME server:
141141
142-
1. Replace the staging annotation on your ingress resource with `certmanager.k8s.io/cluster-issuer: letsencrypt-prod`.
142+
1. Replace the staging annotation on your ingress resource with `cert-manager.io/cluster-issuer: letsencrypt-prod`.
143143
1. Delete the existing staging `ClusterIssuer` resource that you created earlier. Create a new staging resource by replacing the ACME server from the previous `ClusterIssuer` YAML with `https://acme-v02.api.letsencrypt.org/directory`.
144144
145145
Before the Let's Encrypt certificate expires, `cert-manager` automatically updates the certificate in the Kubernetes secret store. At that point, the Application Gateway Ingress Controller applies the updated secret referenced in the ingress resources that it's using to configure Application Gateway.

0 commit comments

Comments
 (0)