Skip to content

Commit c7bd092

Browse files
authored
Merge pull request #95396 from v-maudel/patch-353
M44859: Adding breakline after title to avoid issues in live pages
2 parents 753e0a1 + 915d36c commit c7bd092

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

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

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -138,9 +138,11 @@ Follow the steps below to install [cert-manager](https://docs.cert-manager.io) o
138138
Your browser may warn you of an invalid cert authority. The staging certificate is issued by `CN=Fake LE Intermediate X1`. This is an indication that the system worked as expected and you are ready for your production certificate.
139139
140140
4. Production Certificate
141+
141142
Once your staging certificate is setup successfully you can switch to a production ACME server:
142143
1. Replace the staging annotation on your Ingress resource with: `certmanager.k8s.io/cluster-issuer: letsencrypt-prod`
143144
1. Delete the existing staging `ClusterIssuer` you created in the previous step and create a new one by replacing the ACME server from the ClusterIssuer YAML above with `https://acme-v02.api.letsencrypt.org/directory`
144145
145146
5. Certificate Expiration and Renewal
147+
146148
Before the `Lets Encrypt` certificate expires, `cert-manager` will automatically update the certificate in the Kubernetes secret store. At that point, Application Gateway Ingress Controller will apply the updated secret referenced in the ingress resources it is using to configure the Application Gateway.

0 commit comments

Comments
 (0)