Skip to content

Commit a47cc2c

Browse files
authored
docs(argo-cd): Add AKS Web Application Routing ingress example (#3529)
1 parent 5a59e36 commit a47cc2c

File tree

3 files changed

+56
-2
lines changed

3 files changed

+56
-2
lines changed

charts/argo-cd/Chart.yaml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ appVersion: v3.1.8
33
kubeVersion: ">=1.25.0-0"
44
description: A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.
55
name: argo-cd
6-
version: 8.6.0
6+
version: 8.6.1
77
home: https://github.com/argoproj/argo-helm
88
icon: https://argo-cd.readthedocs.io/en/stable/assets/logo.png
99
sources:
@@ -27,4 +27,4 @@ annotations:
2727
url: https://argoproj.github.io/argo-helm/pgp_keys.asc
2828
artifacthub.io/changes: |
2929
- kind: added
30-
description: Add Gateway API support (HTTPRoute, GRPCRoute, BackendTLSPolicy) - EXPERIMENTAL
30+
description: Add AKS Web Application Routing ingress example

charts/argo-cd/README.md

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -237,6 +237,33 @@ server:
237237
enabled: true
238238
```
239239

240+
### AKS Application Routing (generic)
241+
242+
AKS Web Application Routing uses the standard Kubernetes Ingress specification, so the `generic` controller type is sufficient.
243+
webapprouting provides a managed ingress controller based on nginx.
244+
245+
```yaml
246+
global:
247+
domain: argocd.example.com
248+
249+
configs:
250+
params:
251+
server.insecure: true
252+
253+
server:
254+
ingress:
255+
enabled: true
256+
controller: generic
257+
ingressClassName: webapprouting.kubernetes.azure.com
258+
annotations:
259+
# Optional: Add any AKS-specific annotations if needed
260+
extraTls:
261+
- hosts:
262+
- argocd.example.com
263+
# Certificate can be managed by Web Application Routing
264+
secretName: argocd-tls
265+
```
266+
240267
### Gateway API HTTPRoute
241268

242269
The Gateway API provides a modern, extensible way to configure ingress traffic routing. This chart supports HTTPRoute resources as an alternative to traditional Ingress.

charts/argo-cd/README.md.gotmpl

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -236,6 +236,33 @@ server:
236236
enabled: true
237237
```
238238

239+
### AKS Application Routing (generic)
240+
241+
AKS Web Application Routing uses the standard Kubernetes Ingress specification, so the `generic` controller type is sufficient.
242+
webapprouting provides a managed ingress controller based on nginx.
243+
244+
```yaml
245+
global:
246+
domain: argocd.example.com
247+
248+
configs:
249+
params:
250+
server.insecure: true
251+
252+
server:
253+
ingress:
254+
enabled: true
255+
controller: generic
256+
ingressClassName: webapprouting.kubernetes.azure.com
257+
annotations:
258+
# Optional: Add any AKS-specific annotations if needed
259+
extraTls:
260+
- hosts:
261+
- argocd.example.com
262+
# Certificate can be managed by Web Application Routing
263+
secretName: argocd-tls
264+
```
265+
239266
### Gateway API HTTPRoute
240267

241268
The Gateway API provides a modern, extensible way to configure ingress traffic routing. This chart supports HTTPRoute resources as an alternative to traditional Ingress.

0 commit comments

Comments
 (0)