Skip to content

Updated the AFD/AppRouting TLS blog post to clarify how the TLS secret name is determined` #5531

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
chzbrgr71 merged 4 commits into from
Jan 16, 2026
Merged

Updated the AFD/AppRouting TLS blog post to clarify how the TLS secret name is determined` #5531

Changes from 3 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
432c16e
updated the ingress definition steps to explain how the cert secret n…
swgriffith Jan 6, 2026
8d1f329
updated the ingress definition steps to explain how the cert secret n…
swgriffith Jan 6, 2026
2790518
fixed error raised by URL linter
swgriffith Jan 6, 2026
a3d492d
Update website/blog/2025-02-28-afd-aks-ingress-tls-approuting/index.md
sabbour Jan 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion website/blog/2025-02-28-afd-aks-ingress-tls-approuting/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -227,7 +227,7 @@ Now we can deploy the ingress definition. Look out for the following:

1. The 'tls-cert-keyvault-uri' annotation maps the inbound TLS request to the appropriate certificate secret
2. The 'rules' section maps the target host name to the backend service that should be targeted
3. The 'tls' section will include the target host name and it's mapping to the correct certificate, which we created above
3. The 'tls' section will include the target host name and its mapping to the correct certificate, which is the static value 'keyvault-' followed by the ingress name (i.e. keyvault-aks-helloworld in our case), as documented in the [App Routing TLS Docs](https://learn.microsoft.com/en-us/azure/aks/app-routing-dns-ssl#create-an-ingress-class-that-uses-a-host-name-and-a-certificate-from-azure-key-vault).
Comment thread
sabbour marked this conversation as resolved.
Outdated

```bash
# Get the URI of the certificate
Expand Down