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: site/voyager.md
+28-27Lines changed: 28 additions & 27 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,11 +1,12 @@
1
1
# Load balancing with Voyager/HAProxy
2
2
3
-
This document explains how to set up Voyager to use HAProxy as load balancer to WebLogic domain(s) running in Kubernetes.
3
+
This document explains how to set up Voyager to use the HAProxy as a load balancer for WebLogic domains running in Kubernetes.
4
4
5
-
Voyager is a HAProxybacked ingress controller for Kubernetes. More information about Voyager ingress controller can be found at:https://appscode.com/products/voyager/6.0.0/concepts/.
5
+
Voyager is an HAProxy-backed Ingress controller for Kubernetes. For more information about the Voyager Ingress controller, seehttps://appscode.com/products/voyager/6.0.0/concepts/.
6
6
7
-
## Set up Voyager/HAProxy automatically
8
-
To set up Voyager/HAProxy automatically you can run the create-weblogic-domain.sh script to create a WebLogic domain in Kubernetes. You need to change the domain inputs YAML file first. There are three related properties.
7
+
## Set up the Voyager/HAProxy automatically
8
+
9
+
To set up the Voyager/HAProxy automatically, run the `create-weblogic-domain.sh` script to create a WebLogic domain in Kubernetes. However, first you need to change the domain inputs YAML file. There are three load balancer related properties:
9
10
10
11
```
11
12
...
@@ -19,37 +20,37 @@ loadBalancerWebPort: 30305
19
20
loadBalancerDashboardPort: 30315
20
21
```
21
22
22
-
* The `loadBalancer` property needs to be changed to `VOYAGER`.
23
-
* The `loadBalancerWebPort` property is to specify the `NodePort` number to access the HAProxy load balancer itself.
24
-
* The `loadBalancerDashboardPort` property is to specify the `NodePort` number to access the HAPRoxy stats webpage.
23
+
* The `loadBalancer` property needs to be changed to `VOYAGER`.
24
+
* The `loadBalancerWebPort` property is used to specify the `NodePort` number to access the HAProxy load balancer itself.
25
+
* The `loadBalancerDashboardPort` property is used to specify the `NodePort` number to access the HAPRoxy stats web page.
25
26
26
-
Then after running create-weblogic-domain.sh script, the WebLogic domain is created and the Voyager/HAProxy is also installed and configured properly.
27
-
You can access the HAProxy stats webpage via `http://<hostIP>:30315/` and you'll get a webpage like below.
27
+
Then, after running the `create-weblogic-domain.sh script`, the WebLogic domain is created and the Voyager/HAProxy is also installed and configured properly.
28
+
You can access the HAProxy stats web page using `http://<hostIP>:30315/` and will see a web page like the following:
28
29
29
30
30
31
31
-
After you deploy some application to the WebLogic cluster, you can send requests to the application via`http://<hostIP>:30305/<ctx>/`. The requests are sent to the HAProxy load balancer and the HAProxy will distribute the requests to managed servers of the WebLogic cluster.
32
+
After you deploy an application to the WebLogic cluster, you can send requests to the application using`http://<hostIP>:30305/<ctx>/`. The requests are sent to the HAProxy load balancer and HAProxy will distribute the requests to the Managed Servers of the WebLogic cluster.
32
33
33
34
### What happens underground?
34
35
#### 1. Install the Voyager operator
35
-
The Voyager operator is installed in `voyager` namespace if it hasn't been done before.
36
+
If it hasn't been done before, the Voyager operator is installed in the `voyager` namespace.
36
37
37
-
You should have a voyager-operator-*** pod running in the `voyager` namespace.
38
+
You should have a `voyager-operator-***` pod running in the `voyager` namespace.
And new CRD groups are registered by the Voyager operator.
44
+
New CRD groups are registered by the Voyager operator.
44
45
```
45
46
$ kubectl get crd -l app=voyager
46
47
NAME AGE
47
48
certificates.voyager.appscode.com 8d
48
49
ingresses.voyager.appscode.com 8d
49
50
```
50
-
Now the Voyager operator watches Ingress resources in any namespace.
51
+
Now the Voyager operator watches the Ingress resources in any namespace.
51
52
52
-
#### 2. Create an Voyager Ingress resource
53
+
#### 2. Create a Voyager Ingress resource
53
54
An Ingress resource is generated based on the WebLogic domain configuration and deployed to Kubernetes. Here is an example of what the Voyager Ingress resource might look like for a WebLogic cluster named `cluster-1`, in a domain named `base_domain` with domainUID `domain1`.
54
55
55
56
```yaml
@@ -75,14 +76,14 @@ spec:
75
76
servicePort: '8001'
76
77
```
77
78
78
-
The Kubernetes service named `domain1-cluster-cluster-1` referred by the Ingress resource is also created by create-weblogic-domain.shwhich dynamically includes all the managed servers in the cluster.
79
+
The Kubernetes service named `domain1-cluster-cluster-1`, referred to by the Ingress resource, is also created by the `create-weblogic-domain.sh` script, which dynamically includes all the Managed Servers in the cluster.
A NodePort service is created to expose the HAProxy stats. Following are the example yaml file for the service.
100
+
A NodePort service is created to expose the HAProxy stats. The following is an example YAML file for the service.
101
+
100
102
```yaml
101
103
apiVersion: v1
102
104
kind: Service
@@ -119,12 +121,11 @@ spec:
119
121
origin: voyager
120
122
origin-name: domain1-voyager
121
123
```
122
-
123
-
## Set up Voyager manually to WebLogic domain running in Kubernetes
124
-
You may want to manually set up Voyager to WebLogic domain running in Kubernetes, in cases when some of the default settings of the automatic steps don't meet your requirements, or your WebLogic domain is not created by the WebLogic Operator.
125
-
You need to refer to Voyager documents to do the setup: https://appscode.com/products/voyager/6.0.0/setup/.
126
-
### 1. Install the Voyager operator
127
-
Refer to install guide of Voyager here: install guide: https://appscode.com/products/voyager/6.0.0/setup/install/.
128
-
### 2. Create an Voyager Ingress resource
129
-
Refer to the detail here: https://appscode.com/products/voyager/6.0.0/concepts/overview/. You can choose different types for your Ingress: LoadBalancer, NodePort, HostPort and Internal.
130
124
125
+
## Set up Voyager manually to load balance a WebLogic domain running in Kubernetes
126
+
You may want to manually set up Voyager to load balance a WebLogic domain running in Kubernetes, in cases when some of the default settings of the automatic steps don't meet your requirements, or your WebLogic domain is not created by the WebLogic Operator.
127
+
To do the setup, refer to the Voyager documents at https://appscode.com/products/voyager/6.0.0/setup/.
128
+
### 1. Install the Voyager operator
129
+
Refer to Voyager install guide at https://appscode.com/products/voyager/6.0.0/setup/install/.
130
+
### 2. Create a Voyager Ingress resource
131
+
Refer to the details at https://appscode.com/products/voyager/6.0.0/concepts/overview/. You can choose different types for your Ingress: LoadBalancer, NodePort, HostPort, and Internal.
0 commit comments