Skip to content

Commit 1a7fa3d

Browse files
authored
Update articles/api-management/how-to-self-hosted-gateway-on-kubernetes-in-production.md
1 parent 7a53e19 commit 1a7fa3d

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/api-management/how-to-self-hosted-gateway-on-kubernetes-in-production.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ In order to run the self-hosted gateway in production, there are various aspects
1616

1717
This article provides guidance on how to run [self-hosted gateway](./self-hosted-gateway-overview.md) on Kubernetes for production workloads to ensure that it will run smoothly and reliably.
1818

19-
[!INCLUDE [preview](./includes/preview/preview-callout-self-hosted-gateway-deprecation.md.md)]
19+
[!INCLUDE [preview](./includes/preview/preview-callout-self-hosted-gateway-deprecation.md)]
2020

2121
## Access token
2222
Without a valid access token, a self-hosted gateway can't access and download configuration data from the endpoint of the associated API Management service. The access token can be valid for a maximum of 30 days. It must be regenerated, and the cluster configured with a fresh token, either manually or via automation before it expires.

0 commit comments

Comments
 (0)