Skip to content

Commit 94e18e8

Browse files
committed
modifed examples in type load balancer
1 parent 1850bf7 commit 94e18e8

2 files changed

Lines changed: 7 additions & 10 deletions

File tree

docs/configure/service-type-lb-solution-in-aws.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,8 @@ When you deploy a service in AWS, a load balancer is created automatically and t
1010

1111
Citrix IPAM controller is used to automatically allocate IP addresses to services of type LoadBalancer from a specified range of IP addresses. For more information about the Citrix solution for services of type LoadBalancer, see [Expose services of type LoadBalancer](https://github.com/citrix/citrix-k8s-ingress-controller/blob/ef929526a1bd23f30a8677d4494c600f21b7b2a8/docs/network/type_loadbalancer.md).
1212

13+
You can deploy the Citrix solution for service of type LoadBalancer in AWS using Helm charts or YAML files.
14+
1315
**Prerequisites**
1416

1517
- Ensure that the Elastic Kubernetes Service (EKS) cluster version 1.18 or later is running.
@@ -43,7 +45,7 @@ Perform the following steps to configure the Citrix solution for service of type
4345

4446
kubectl create -f https://github.com/citrix/citrix-k8s-ingress-controller/blob/master/docs/how-to/typeLB/aws/guestbook-all-in-one-lb.yaml
4547

46-
**Note**: The `guestbook` microservice is a sample used in this procedure. You can deploy an application of your choice. Ensure that the service should be of type LoadBalancer and the service manifest should contain the annotation.
48+
**Note**: The `guestbook` microservice is a sample used in this procedure. You can deploy an application of your choice. Ensure that the service should be of type LoadBalancer and the service manifest should contain the annotation.
4749

4850
1. Associate an elastic IP address with the VIP of Citrix ADC VPX.
4951

@@ -77,7 +79,7 @@ Perform the following steps to deploy the Citrix solution for service of type Lo
7779

7880
1. Deploy the IPAM controller. For information about deploying the IPAM controller, see [Deploy the IPAM controller](https://github.com/citrix/citrix-k8s-ingress-controller/blob/c683c72457e1be74718f72c2f26bbe57105133a2/docs/network/type_loadbalancer.md#step3-deploy-the-ipam-controller).
7981

80-
**Note**: Specify the list of Citrix ADC VPX VIPs in the **VIP_RANGE** field of the IPAM deployment YAML file.
82+
**Note**: Specify the list of Citrix ADC VPX VIPs in the **VIP_RANGE** field of the IPAM deployment YAML file.
8183

8284
1. Deploy the application with service type LoadBalancer in Amazon EKS using the following steps:
8385

@@ -89,7 +91,7 @@ Perform the following steps to deploy the Citrix solution for service of type Lo
8991

9092
kubectl create -f https://github.com/citrix/citrix-k8s-ingress-controller/blob/master/docs/how-to/typeLB/aws/guestbook-all-in-one-lb.yaml
9193

92-
**Note**: The `guestbook` microservice is a sample used in this procedure. You can deploy an application of your choice. Ensure that the service should be of type LoadBalancer and the service manifest should contain the annotation.
94+
**Note**: The `guestbook` microservice is a sample used in this procedure. You can deploy an application of your choice. Ensure that the service should be of type LoadBalancer and the service manifest should contain the annotation.
9395

9496
1. Associate an elastic IP address with the VIP of Citrix ADC VPX.
9597

docs/network/type_loadbalancer.md

Lines changed: 2 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -285,10 +285,7 @@ Perform the following to create a service (`apache`) of type `LoadBalancer`.
285285
name: apache
286286
spec:
287287
externalTrafficPolicy: Local
288-
loadBalancerIP: "110.217.212.16"
289288
type: LoadBalancer
290-
selector:
291-
name: apache
292289
ports:
293290
- name: http
294291
port: 80
@@ -332,7 +329,7 @@ You can also expose a service of type LoadBalancer manually by specifying an IP
332329

333330
When you create a service of type [LoadBalancer](https://kubernetes.io/docs/concepts/services-networking/service/#loadbalancer), the Citrix ingress controller configures the IP address you have defined in the `spec.loadBalancerIP` field as a virtual IP (VIP) address in Citrix ADC.
334331

335-
### **Example:** Expose an Apache application using service of type LoadBalancer
332+
### **Example:** Expose an Apache application using service of type LoadBalancer by specifying an IP address
336333

337334
Perform the following:
338335

@@ -396,10 +393,8 @@ Perform the following:
396393
name: apache
397394
spec:
398395
externalTrafficPolicy: Local
399-
loadBalancerIP: "110.217.212.16"
396+
loadBalancerIP: "10.217.212.16"
400397
type: LoadBalancer
401-
selector:
402-
name: apache
403398
ports:
404399
- name: http
405400
port: 80

0 commit comments

Comments
 (0)