Skip to content

Commit d0d0e32

Browse files
authored
Merge pull request #238 from oracle/RMtraefik
minor edits
2 parents 321ccdb + 2c4823b commit d0d0e32

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

site/traefik.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
# Load balancing with Traefik
22

3-
If the `loadBalancer` option is set to `traefik` when running the `create-weblogic-domain.sh` script to create a WebLogic domain in Kubernetes, then the Traefik Ingress Controller will be installed into the *cluster* and an *ingress* will be created for each WebLogic *cluster* in the *domain*.
3+
If the `loadBalancer` option is set to `traefik` when running the `create-weblogic-domain.sh` script to create a WebLogic domain in Kubernetes, then the Traefik Ingress Controller will be installed into the cluster and an Ingress will be created for each WebLogic cluster in the domain.
44

55
More information about the Traefik Ingress controller can be found at: [https://docs.traefik.io/user-guide/kubernetes/](https://docs.traefik.io/user-guide/kubernetes/)
66

7-
Traefik will expose two `NodePorts` that allow access to the Ingress itself and to the Traefik admin UI. The ports are controlled by these settings in the domain inputs YAML file:
7+
Traefik will expose two `NodePorts` that allow access to the Ingress itself and to the Traefik Web UI. The ports are controlled by these settings in the domain inputs YAML file:
88

99
```
1010
# Load balancer web port
@@ -13,7 +13,7 @@ loadBalancerWebPort: 30305
1313
# Load balancer dashboard port
1414
loadBalancerDashboardPort: 30315
1515
```
16-
The operator will automatically update the Ingress to ensure that it contains a list of only those pods that are "ready". Here is an example of what the Ingress might look like for a WebLogic cluster called `cluster-1`, in a domain called `base_domain` with `domainUID domain1` that has three Managed Servers in the "ready" state:
16+
The operator will automatically update the Ingress to ensure that it contains a list of only those pods that are "ready". Here is an example of what the Ingress might look like for a WebLogic cluster called `cluster-1`, in a domain called `base_domain`, with `domainUID domain1`, that has three Managed Servers in the "ready" state:
1717

1818
```
1919
apiVersion: extensions/v1beta1
@@ -46,4 +46,4 @@ spec:
4646
path: /
4747
```
4848

49-
Notice that currently the only supported type of load balancing is using the root path ("`/`"). As such, there is one instance of Traefik for each WebLogic cluster. Please take a look at our [wish list](https://github.com/oracle/weblogic-kubernetes-operator/wiki/Wish-list) to get an idea of the load balancing improvements we would like to do.
49+
Notice that currently the only supported type of load balancing is using the root path ("`/`"). As such, there is one instance of Traefik for each WebLogic cluster.

0 commit comments

Comments
 (0)