This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(153.6, 34%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAS%3C/text%3E%3C/svg%3E)
I am using an Azure managed AKS and Appgateway setup. I am trying to increase the request timeout from "30" (which seems to be the default value) to "60". I have followed this document https://azure.github.io/application-gateway-kubernetes-ingress/annotations/ and added the following annotation line in my ingress file:
appgw.ingress.kubernetes.io/request-timeout: "60"
The top part of my ingresses looks like this
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: x.x.x.x.com
annotations:
kubernetes.io/ingress.class: azure/application-gateway
appgw.ingress.kubernetes.io/appgw-ssl-certificate: Dev-Portal
appgw.ingress.kubernetes.io/rewrite-rule-set: Custom-Rule-SEt
appgw.ingress.kubernetes.io/health-probe-hostname: x.x.x.x.com
appgw.ingress.kubernetes.io/health-probe-path: /healthz
appgw.ingress.kubernetes.io/request-timeout: "60"
However, this does not seem to take effect. Can you please help me ?
Thank you
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(268.8, 61%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGV%3C/text%3E%3C/svg%3E)
Hi Anjana Silva,
Your annotation format is correct, but if appgw.ingress.kubernetes.io/request-timeout: "60" is not taking effect, try this troubleshooting steps :
Run the following command to check if AGIC is applying the changes:
kubectl get ingress -A -o yaml | grep request-timeout
If the annotation is missing, reapply the Ingress manifest and check AGIC logs:
kubectl logs -n kube-system -l app=ingress-azure
Go to Azure Portal → Application Gateway → HTTP Settings and verify if the timeout is updated. If not, AGIC may not have reconciled the changes.
Restart AGIC to ensure it picks up the changes:
kubectl delete pod -n kube-system -l app=ingress-azure
Run the following to check the AGIC version:
kubectl get pods -n kube-system | grep ingress-azure
If using an outdated version, consider upgrading.
For more details, refer to documentation
https://learn.microsoft.com/en-us/azure/application-gateway/ingress-controller-annotations
If you have any further queries, please let us know we are glad to help you.
If it was helpful, please click "Upvote" on this post to let us know.
Thank You.
@ Geethasri.V : Thanks for your reply.
Unfortunately, changing to an integer did not work.
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: x.x.x.x.com
annotations:
kubernetes.io/ingress.class: azure/application-gateway
appgw.ingress.kubernetes.io/appgw-ssl-certificate: Dev-Portal
appgw.ingress.kubernetes.io/rewrite-rule-set: Custom-Rule-SEt
appgw.ingress.kubernetes.io/health-probe-hostname: x.x.x.x.com
appgw.ingress.kubernetes.io/health-probe-path: /healthz
appgw.ingress.kubernetes.io/request-timeout: 60
I have checked the AGIC version by describing the pod. AGIC version is 1.7.2
I have waited for some time, and I can still see its 30 seconds when I view the record using the Azure portal.
What would you suggest we do next?
Thank you
Hi @ Geethasri.V : Thanks for your reply.
What do you suggest I do next?
Thanks
Hi Anjana Silva,
It looks like AGIC is not applying the request timeout change. Here are the next steps to troubleshoot and resolve the issue:
Revert the Annotation to a String Kubernetes annotations should always be strings. Change it back to:
appgw.ingress.kubernetes.io/request-timeout: "60"
Reapply the Ingress configuration:
kubectl apply -f <your-ingress-file>.yaml
Check AGIC Logs for Errors Run the following command to check if AGIC is processing the annotation correctly:
kubectl logs -n kube-system -l app=ingress-azure
Look for any warnings or errors related to request-timeout.
Verify the Timeout in Application Gateway After reapplying, check if the timeout is reflected in Azure Portal → Application Gateway → HTTP Settings.
If it still shows 30 seconds, the change might not have been propagated.
Restart AGIC to Force Sync
If AGIC is not picking up the changes, restart it:
kubectl delete pod -n kube-system -l app=ingress-azure
This forces AGIC to reconcile the configuration.
Verify AGIC Permissions AGIC requires proper permissions to modify the Application Gateway. Verify that AGIC’s managed identity has the necessary Contributor or Application Gateway Contributor role on the resource.
You can check this in Azure Portal → Application Gateway → Access control (IAM).
If the issue persists, manually update the timeout in Application Gateway HTTP settings as a temporary workaround.
If you have any further queries, please let us know we are glad to help you.
If it was helpful, please click "Upvote" on this post to let us know.
Thank You.