Skip to content

Commit e6b1ef3

Browse files
authored
Merge pull request #490 from apoorva-05/master
Updated Alternate Backend Documentation
2 parents af32b4e + a23d064 commit e6b1ef3

1 file changed

Lines changed: 34 additions & 2 deletions

File tree

docs/deploy/deploy-cic-openshift.md

Lines changed: 34 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -32,8 +32,40 @@ For information on deploying the Citrix ingress controller to control the OpenSh
3232

3333
You can use Citrix ADC for load balancing Openshift control plane (master nodes). Citrix provides a solution to automate the configuration of Citrix ADC using Terraform instead of manually configuring the Citrix ADC. For more information, see [Citrix ADC as a load balancer for the OpenShift control plane](https://github.com/citrix/citrix-k8s-ingress-controller/blob/master/deployment/openshift/citrix-adc-for-control-plane/README.md).
3434

35-
**Note:**
36-
OpenShift support of alternate backends is now supported by Citrix ingress controller. Citrix ADC is configured according to the weights provided in the routes definition and traffic is distributed among the service pods based on those weights.
35+
## Alternate Backend Support
36+
[OpenShift Alternate backends](https://docs.openshift.com/container-platform/3.7/architecture/networking/routes.html#alternateBackends) is now supported by Citrix ingress controller.
37+
38+
Citrix ADC is configured according to the weights provided in the routes definition and traffic is distributed among the service pods based on those weights.
39+
40+
The following is an example of a route manifest with alternate backend:
41+
42+
43+
kind: Route
44+
apiVersion: route.openshift.io/v1
45+
metadata:
46+
name: r1
47+
labels:
48+
name: apache
49+
annotations:
50+
ingress.citrix.com/frontend-ip: "<Frontend-ip>"
51+
spec:
52+
host: some.alternate-backends.com
53+
to:
54+
kind: Service
55+
name: apache-1
56+
weight: 30
57+
alternateBackends:
58+
- kind: Service
59+
name: apache-2
60+
weight: 20
61+
- kind: Service
62+
name: apache-3
63+
weight: 50
64+
port:
65+
targetPort: 80
66+
wildcardPolicy: None
67+
68+
For this route, 30 percent of the traffic is sent to the service apache-1 and 20 percent is sent to the service apache2 and 50 percent to the service apache-3 based on weights provided in the route manifest
3769

3870
## Supported Citrix components on OpenShift
3971

0 commit comments

Comments
 (0)