Skip to content

Commit de7b9f8

Browse files
authored
Update ingress-controller-install-new.md
1. Kestrel listens to the port 8080. Azure App Gateway Backend is unhealthy because of Port 80 mentioned in Pod's Container Port and Service definition's TargetPort. 2. Ingress Controller definition throw error because of the missing pathType property.
1 parent 266c208 commit de7b9f8

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

articles/application-gateway/ingress-controller-install-new.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -293,7 +293,7 @@ spec:
293293
- image: "mcr.microsoft.com/dotnet/core/samples:aspnetapp"
294294
name: aspnetapp-image
295295
ports:
296-
- containerPort: 80
296+
- containerPort: 8080
297297
protocol: TCP
298298
299299
---
@@ -308,7 +308,7 @@ spec:
308308
ports:
309309
- protocol: TCP
310310
port: 80
311-
targetPort: 80
311+
targetPort: 8080
312312
313313
---
314314
@@ -323,6 +323,7 @@ spec:
323323
- http:
324324
paths:
325325
- path: /
326+
pathType: Exact
326327
backend:
327328
serviceName: aspnetapp
328329
servicePort: 80
@@ -346,4 +347,4 @@ kubectl apply -f aspnetapp.yaml
346347
347348
## Other Examples
348349
This [how-to guide](ingress-controller-expose-service-over-http-https.md) contains more examples on how to expose an AKS
349-
service via HTTP or HTTPS, to the Internet with Application Gateway.
350+
service via HTTP or HTTPS, to the Internet with Application Gateway.

0 commit comments

Comments
 (0)