Skip to content
You are viewing the latest documentation for Solo Enterprise for kgateway. To access the documentation for older versions, use the version switcher.

For the complete documentation index, see llms.txt. Markdown versions of all docs pages are available by appending .md to any docs URL.

About

Page as Markdown

Learn how retries are triggered, budgeted, and applied across routes.

A retry is the number of times a request is retried if it fails. This setting can be useful to avoid your apps from failing if they are temporarily unavailable. With retries, calls are retried a certain number of times before they are considered failed. Retries can enhance your app’s availability by making sure that calls don’t fail permanently because of transient problems, such as a temporarily overloaded service or network.

Configuration options

You can configure retries by using a Kubernetes Gateway API-native configuration or a EnterpriseKgatewayTrafficPolicy as shown in the following table

Type of timeoutDescriptionConfigured viaAttach to
Request retriesSpecify the number of times and duration for the gateway to try a connection to an unresponsive backend service.
  • HTTPRoute
  • EnterpriseKgatewayTrafficPolicy
  • HTTPRoute
  • HTTPRoute rule
  • Gateway listener (EnterpriseKgatewayTrafficPolicy only)
Per-try timeoutSet a shorter timeout for retries than the overall request timeout.
  • HTTPRoute
  • EnterpriseKgatewayTrafficPolicy
  • HTTPRoute
  • HTTPRoute rule
  • Gateway listener (EnterpriseKgatewayTrafficPolicy only)

Was this page helpful?