Skip to content

Commit 3a658a1

Browse files
committed
fix tabs
1 parent b13d45a commit 3a658a1

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

articles/application-gateway/for-containers/how-to-cert-manager-lets-encrypt-ingress-api.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -88,6 +88,7 @@ spec:
8888
alb.networking.azure.io/alb-namespace: alb-test-infra
8989
EOF
9090
```
91+
---
9192

9293
# [Bring your own (BYO) deployment](#tab/byo)
9394

@@ -152,7 +153,7 @@ The status should show `True` and type `Ready` under conditions.
152153
status: "True"
153154
type: Ready
154155
```
155-
156+
---
156157
## Deploy the required Ingress resource
157158
158159
# [ALB managed deployment](#tab/alb-managed)
@@ -200,7 +201,7 @@ spec:
200201
# number: 8080
201202
EOF
202203
```
203-
204+
---
204205
# [Bring your own (BYO) deployment](#tab/byo)
205206

206207
1. Set the following environment variables
@@ -326,8 +327,8 @@ The environment is now configured to route traffic to the sample application usi
326327
curl https://backend-v1.contoso.com -v 2>&1 | grep issuer
327328
```
328329

329-
Upon result, you should see
330+
You should see the following output:
330331

331332
`* issuer: C=US; O=Let's Encrypt; CN=R11`
332333

333-
You have successfully completed the following steps: installed the ALB Controller, deployed a backend application, obtained a certificate from Let's Encrypt using cert-manager, and configured traffic routing to the application through Application Gateway for Containers
334+
You have successfully installed the ALB Controller, deployed a backend application, obtained a certificate from Let's Encrypt using cert-manager, and configured traffic routing to the application through Application Gateway for Containers.

0 commit comments

Comments
 (0)