docs(DXM-100): add shared Redis TLS config component to feature pages

Refactor the Redis TLS configuration documentation into a reusable shared
MDX component (docs/shared/redis-tls.mdx) and include it on every feature
page that exposes Redis configuration—APQ, query plan caching, response
cache customization, and the TLS overview—so users discover the TLS option
contextually rather than only on the overview page.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: bignimbus

docs/shared/redis-tls.mdx

@@ -1,16 +1,15 @@
-For Redis TLS connections, you can set up a client certificate or override the root certificate authority by configuring `tls` in your router's [YAML config file](https://www.apollographql.com/docs/router/overview/#yaml-config-file). For example:
+For Redis TLS connections, you can set up a client certificate or override the root certificate authority by configuring `tls` in your router's [YAML config file](/graphos/routing/configuration/overview#yaml-config-file). Nest the `tls` configuration under the `redis` section for your feature. For example:
 
 ```yaml
-apq:
-  router:
-    cache:
-      redis:
-        urls: [ "rediss://redis.example.com:6379" ]
-        #highlight-start
-        tls:
-          certificate_authorities: ${file./path/to/ca.crt}
-          client_authentication:
-            certificate_chain: ${file./path/to/certificate_chain.pem}
-            key: ${file./path/to/key.pem}
-        #highlight-end
+redis:
+  urls: ["rediss://redis.example.com:6379"]
+  #highlight-start
+  tls:
+    certificate_authorities: ${file./path/to/ca.crt}
+    client_authentication:
+      certificate_chain: ${file./path/to/certificate_chain.pem}
+      key: ${file./path/to/key.pem}
+  #highlight-end
 ```
+
+For comprehensive TLS configuration details, including client-side and subgraph TLS, see [TLS configuration](/router/configuration/tls).

docs/source/routing/operations/apq.mdx

@@ -4,6 +4,8 @@ subtitle: Configure caching for automatic persisted queries
 description: Configure automatic persisted queries (APQ) in GraphOS Router to reduce network usage by sending query hashes instead of full query strings.
 ---
 
+import RedisTls from '../../../shared/redis-tls.mdx';
+
 [Automatic Persisted Queries (**APQ**)](/apollo-server/performance/apq) enable GraphQL clients to send a server the _hash_ of their query string, _instead of_ sending the query string itself. When query strings are very large, this can significantly reduce network usage.
 
 The router supports using APQ in its communications with both clients _and_ subgraphs:
@@ -198,20 +200,7 @@ When using the same Redis instance for multiple purposes, the `namespace` option
 
 #### TLS
 
-For Redis TLS connections, you can set up a client certificate or override the root certificate authority by configuring `tls` in your router's [YAML config file](/graphos/routing/configuration/overview#yaml-config-file). For example:
-
-```yaml
-apq:
-  router:
-    cache:
-      redis:
-        urls: ["rediss://redis.example.com:6379"]
-        tls:
-          certificate_authorities: ${file./path/to/ca.crt}
-          client_authentication:
-            certificate_chain: ${file./path/to/certificate_chain.pem}
-            key: ${file./path/to/key.pem}
-```
+<RedisTls />
 
 #### Required to start
 

docs/source/routing/performance/caching/response-caching/customization.mdx

@@ -5,6 +5,8 @@ description: Configure per-user caching with private data, create custom cache k
 minVersion: Router v2.10.0
 ---
 
+import RedisTls from '../../../../../shared/redis-tls.mdx';
+
 Beyond basic response caching, the router supports customization for caching private data, modifying cache keys, and advanced Redis configuration.
 
 ## When to customize
@@ -254,28 +256,7 @@ or, if configured with multiple URLs:
 
 ### TLS and authentication
 
-For Redis TLS connections, you can set up a client certificate or override the root certificate authority by configuring `tls` in your router's [YAML config file](https://www.apollographql.com/docs/router/overview/#yaml-config-file). For example:
-
-```yaml title="router.yaml"
-# Enable response caching globally
-response_cache:
-  enabled: true
-  subgraph:
-    all:
-      enabled: true
-      # Configure Redis globally
-      redis:
-        urls: [ "rediss://redis.example.com:6379" ]
-        #highlight-start
-        username: root
-        password: ${env.REDIS_PASSWORD}
-        tls:
-          certificate_authorities: ${file./path/to/ca.crt}
-          client_authentication:
-            certificate_chain: ${file./path/to/certificate_chain.pem}
-            key: ${file./path/to/key.pem}
-        #highlight-end
-```
+<RedisTls />
 
 ### Timeout configuration
 

docs/source/routing/query-planning/caching.mdx

@@ -4,6 +4,8 @@ subtitle: Configure in-memory and distributed caching for query plans
 description: Configure query plan caching to improve router performance by storing generated query plans in memory or Redis.
 ---
 
+import RedisTls from '../../../shared/redis-tls.mdx';
+
 Whenever your router receives an incoming GraphQL operation, it generates a [query plan](/graphos/resources/federation/query-plans) to determine which subgraphs it needs to query to resolve that operation.
 
 By caching previously generated query plans, your router can skip generating them again if a client later sends the exact same operation—improving your router's responsiveness.
@@ -243,20 +245,7 @@ When using the same Redis instance for multiple purposes, the `namespace` option
 
 #### TLS
 
-For Redis TLS connections, you can set up a client certificate or override the root certificate authority by configuring `tls` in your router's [YAML config file](/graphos/routing/configuration/overview#yaml-config-file). For example:
-
-```yaml
-supergraph:
-  query_planning:
-    cache:
-      redis:
-        urls: ["rediss://redis.example.com:6379"]
-        tls:
-          certificate_authorities: ${file./path/to/ca.crt}
-          client_authentication:
-            certificate_chain: ${file./path/to/certificate_chain.pem}
-            key: ${file./path/to/key.pem}
-```
+<RedisTls />
 
 #### Required to start
 

docs/source/routing/security/tls.mdx

@@ -5,6 +5,8 @@ redirectFrom:
   - /router/configuration/overview/#tls
 ---
 
+import RedisTls from '../../../shared/redis-tls.mdx';
+
 The GraphOS Router supports TLS to authenticate and encrypt communications, both on the client side and the subgraph side. It works automatically on the subgraph side if the subgraph URL starts with `https://`.
 
 ```yaml title="Example TLS configuration"
@@ -128,19 +130,4 @@ tls:
 
 ## Redis TLS configuration
 
-For Redis TLS connections, you can set up a client certificate or override the root certificate authority by configuring `tls` in your router's [YAML config file](https://www.apollographql.com/docs/router/overview/#yaml-config-file). For example:
-
-```yaml
-apq:
-  router:
-    cache:
-      redis:
-        urls: [ "rediss://redis.example.com:6379" ]
-        #highlight-start
-        tls:
-          certificate_authorities: ${file./path/to/ca.crt}
-          client_authentication:
-            certificate_chain: ${file./path/to/certificate_chain.pem}
-            key: ${file./path/to/key.pem}
-        #highlight-end
-```
+<RedisTls />