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/ingress.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,20 +24,20 @@ After the Ingress controller is running, it monitors Ingress resources in given
24
24
1. Install Ingress Resource(s)
25
25
Ingress resources contain routing rules to one or more backends. And Ingress controller is responsible to apply the rules to the underline load balancer.
26
26
There are two approaches to create the Ingress resource:
27
-
1. Use the helm chart [ingress-per-domain](kubernetes/samples/charts/ingress-per-domain).
27
+
1. Use the helm chart [ingress-per-domain](../kubernetes/samples/charts/ingress-per-domain).
28
28
Each Ingress provider support a bunch of different annotations in Ingress resources. This helm chart allows you to define the routing rules without dealing with the detailed provider-specific annotations. Currently we support two Ingress providers: Traefik and Voyager. The limitation of the helm chart is that it only support one WebLogic cluster as the backend.
29
29
30
30
1. Create and install the Ingress yaml manually.
31
31
Manually edit the Ingress yaml file and then install it to the k8s cluster.
32
32
33
33
## Guide and samples for Traefik and Voyager/HAProxy
34
34
Traefik and Voyager/HAProxy are both popular Ingress providers. We provide detail guide to install and configure these two Ingress providers, specially in front of WebLogic domain(s).
We also provide Ingress samples for these two Ingress providers, with multiple WebLogic clusters as the backends and covering different routing rules, host-routing and path-routing, and TLS termination.
0 commit comments