You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/multicluster/multi-cluster.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -256,6 +256,10 @@ For a sample configuration of multi-cloud ingress and load balancing solution fo
256
256
257
257
## How to direct the DNS resolution of pods to Citrix GSLB ADC
258
258
259
+
**Note:** This procedure is optional and needed only if the pods within the cluster need to resolve the DNS through the Citrix GSLB ADC.
260
+
261
+
### When pods are within the Kubernetes cluster
262
+
259
263
When you want the pods in a Kubernetes cluster to use the GSLB solution, the ConfigMap of the DNS provider should be updated to forward the request for a domain (for which GSLB is required) to Citrix GSLB ADC.
260
264
261
265
The following example shows how to update the ConfigMap if the DNS provider is CoreDNS.
@@ -307,7 +311,7 @@ The IP address specified (`forward . 10.102.217.149`) is a DNS service configure
307
311
308
312
forward . ip1 ip2 ip3
309
313
310
-
##Directing the DNS resolution of pods to Citrix GSLB ADC in OpenShift
314
+
### When pods are within the OpenShift cluster
311
315
312
316
When you want the pods in an OpenShift cluster to use the GSLB solution, the DNS operator should be updated to forward the request for a domain (for which GSLB is required) to Citrix GSLB ADC.
0 commit comments