diff --git a/linkerd.io/content/2-edge/tasks/configuring-retries.md b/linkerd.io/content/2-edge/tasks/configuring-retries.md index f4c09e0908..a19076f281 100644 --- a/linkerd.io/content/2-edge/tasks/configuring-retries.md +++ b/linkerd.io/content/2-edge/tasks/configuring-retries.md @@ -34,8 +34,8 @@ for a tutorial of how to configure retries. ## Retries -For routes that are idempotent and don't have bodies, you can edit the service -profile and add `isRetryable` to the retryable route: +For routes that are idempotent, you can edit the service profile and add +`isRetryable` to the retryable route: ```yaml spec: @@ -47,6 +47,13 @@ spec: isRetryable: true ### ADD THIS LINE ### ``` +Retries are supported for _all_ idempotent requests, whatever verb they use, +and [whether or not they have a body]. In particular, this mean that gRPC +requests can be retried. However, requests will not be retried if the body +exceeds 64KiB. + +[whether or not they have a body]:../../../2021/10/26/how-linkerd-retries-http-requests-with-bodies/ + ## Retry Budgets A retry budget is a mechanism that limits the number of retries that can be diff --git a/linkerd.io/content/2.11/tasks/configuring-retries.md b/linkerd.io/content/2.11/tasks/configuring-retries.md index 942d500ddd..f6628c1b92 100644 --- a/linkerd.io/content/2.11/tasks/configuring-retries.md +++ b/linkerd.io/content/2.11/tasks/configuring-retries.md @@ -26,8 +26,8 @@ for a tutorial of how to configure retries. ## Retries -For routes that are idempotent and don't have bodies, you can edit the service -profile and add `isRetryable` to the retryable route: +For routes that are idempotent, you can edit the service profile and add +`isRetryable` to the retryable route: ```yaml spec: @@ -39,6 +39,13 @@ spec: isRetryable: true ### ADD THIS LINE ### ``` +Retries are supported for _all_ idempotent requests, whatever verb they use, +and [whether or not they have a body]. In particular, this mean that gRPC +requests can be retried. However, requests will not be retried if the body +exceeds 64KiB. + +[whether or not they have a body]:../../../2021/10/26/how-linkerd-retries-http-requests-with-bodies/ + ## Retry Budgets A retry budget is a mechanism that limits the number of retries that can be diff --git a/linkerd.io/content/2.12/tasks/configuring-retries.md b/linkerd.io/content/2.12/tasks/configuring-retries.md index ff46725d7d..45d3810c6c 100644 --- a/linkerd.io/content/2.12/tasks/configuring-retries.md +++ b/linkerd.io/content/2.12/tasks/configuring-retries.md @@ -34,8 +34,8 @@ for a tutorial of how to configure retries. ## Retries -For routes that are idempotent and don't have bodies, you can edit the service -profile and add `isRetryable` to the retryable route: +For routes that are idempotent, you can edit the service profile and add +`isRetryable` to the retryable route: ```yaml spec: @@ -47,6 +47,13 @@ spec: isRetryable: true ### ADD THIS LINE ### ``` +Retries are supported for _all_ idempotent requests, whatever verb they use, +and [whether or not they have a body]. In particular, this mean that gRPC +requests can be retried. However, requests will not be retried if the body +exceeds 64KiB. + +[whether or not they have a body]:../../../2021/10/26/how-linkerd-retries-http-requests-with-bodies/ + ## Retry Budgets A retry budget is a mechanism that limits the number of retries that can be diff --git a/linkerd.io/content/2.13/tasks/configuring-retries.md b/linkerd.io/content/2.13/tasks/configuring-retries.md index ff46725d7d..45d3810c6c 100644 --- a/linkerd.io/content/2.13/tasks/configuring-retries.md +++ b/linkerd.io/content/2.13/tasks/configuring-retries.md @@ -34,8 +34,8 @@ for a tutorial of how to configure retries. ## Retries -For routes that are idempotent and don't have bodies, you can edit the service -profile and add `isRetryable` to the retryable route: +For routes that are idempotent, you can edit the service profile and add +`isRetryable` to the retryable route: ```yaml spec: @@ -47,6 +47,13 @@ spec: isRetryable: true ### ADD THIS LINE ### ``` +Retries are supported for _all_ idempotent requests, whatever verb they use, +and [whether or not they have a body]. In particular, this mean that gRPC +requests can be retried. However, requests will not be retried if the body +exceeds 64KiB. + +[whether or not they have a body]:../../../2021/10/26/how-linkerd-retries-http-requests-with-bodies/ + ## Retry Budgets A retry budget is a mechanism that limits the number of retries that can be diff --git a/linkerd.io/content/2.14/tasks/configuring-retries.md b/linkerd.io/content/2.14/tasks/configuring-retries.md index f4c09e0908..a19076f281 100644 --- a/linkerd.io/content/2.14/tasks/configuring-retries.md +++ b/linkerd.io/content/2.14/tasks/configuring-retries.md @@ -34,8 +34,8 @@ for a tutorial of how to configure retries. ## Retries -For routes that are idempotent and don't have bodies, you can edit the service -profile and add `isRetryable` to the retryable route: +For routes that are idempotent, you can edit the service profile and add +`isRetryable` to the retryable route: ```yaml spec: @@ -47,6 +47,13 @@ spec: isRetryable: true ### ADD THIS LINE ### ``` +Retries are supported for _all_ idempotent requests, whatever verb they use, +and [whether or not they have a body]. In particular, this mean that gRPC +requests can be retried. However, requests will not be retried if the body +exceeds 64KiB. + +[whether or not they have a body]:../../../2021/10/26/how-linkerd-retries-http-requests-with-bodies/ + ## Retry Budgets A retry budget is a mechanism that limits the number of retries that can be