remove Voyager support in docs (#2556)

Author: rosemarymarano

documentation/staging/content/faq/oci-lb.md

@@ -7,14 +7,14 @@ description: "If you are running your Kubernetes cluster on Oracle Container Eng
 for Kubernetes (OKE), then you can have OCI automatically
 provision load balancers for you by creating a `Service` of type
 `LoadBalancer` instead of (or in addition to) installing an
-ingress controller like Traefik or Voyager."
+ingress controller like Traefik."
 ---
 
 If you are running your Kubernetes cluster on Oracle Container Engine
 for Kubernetes (commonly known as OKE), then you can have OCI automatically
 provision load balancers for you by creating a `Service` of type
 `LoadBalancer` instead of (or in addition to) installing an
-ingress controller like Traefik or Voyager.
+ingress controller like Traefik.
 
 OKE Kubernetes worker nodes typically do not have public IP addresses.
 This means that the `NodePort` services created by the operator are

documentation/staging/content/samples/ingress/_index.md

@@ -6,17 +6,16 @@ description: "Ingress controllers and load balancer sample scripts."
 ---
 
 
-The WebLogic Kubernetes Operator supports NGINX, Traefik, Voyager, and Apache. We provide samples that demonstrate how to install and configure each one.
+The WebLogic Kubernetes Operator supports NGINX, Traefik, and Apache. We provide samples that demonstrate how to install and configure each one.
 
 {{% notice note %}}
-For production environments, we recommend NGINX, Voyager, Traefik (2.2.1 or later) ingress controllers, Apache, or the load balancer provided by your cloud provider.
+For production environments, we recommend NGINX, Traefik (2.2.1 or later) ingress controllers, Apache, or the load balancer provided by your cloud provider.
 {{% /notice %}}
 
 
 The samples are located in following folders:
 
 * [Traefik](https://github.com/oracle/weblogic-kubernetes-operator/blob/main/kubernetes/samples/charts/traefik/README.md)
-* [Voyager](https://github.com/oracle/weblogic-kubernetes-operator/blob/main/kubernetes/samples/charts/voyager/README.md)
 * [NGINX](https://github.com/oracle/weblogic-kubernetes-operator/blob/main/kubernetes/samples/charts/nginx/README.md)
 * Apache-samples/[custom-sample](https://github.com/oracle/weblogic-kubernetes-operator/blob/main/kubernetes/samples/charts/apache-samples/custom-sample/README.md)
 * Apache-samples/[default-sample](https://github.com/oracle/weblogic-kubernetes-operator/blob/main/kubernetes/samples/charts/apache-samples/default-sample/README.md)

documentation/staging/content/userguide/managing-domains/ingress/_index.md

@@ -7,7 +7,7 @@ pre = "<b> </b>"
 
 Ingresses are one approach provided by Kubernetes to configure load balancers.
 Depending on the version of Kubernetes you are using, and your cloud provider, you may need to use Ingresses.
-For more information about Ingresses, see [the Ingress documentation](https://kubernetes.io/docs/concepts/services-networking/ingress/).  
+For more information about Ingresses, see the [Kubernetes Ingress](https://kubernetes.io/docs/concepts/services-networking/ingress/) documentation.  
 
 #### WebLogic clusters as backends of an Ingress
 
@@ -34,7 +34,7 @@ The service, `serviceName` and `servicePort`, of a WebLogic cluster will be used
 object and the load balancer will route traffic to the WebLogic Servers within the cluster based on the rules.
 
 {{% notice note %}}
-Most common ingress controllers, for example Traefik, Voyager, and NGINX,
+Most common ingress controllers, for example Traefik and NGINX,
 understand that there are zero or more actual pods behind the service, and they actually
 build their backend list and route requests to those backends directly, not through the service.  This means that
 requests are properly balanced across the pods, according to the load balancing algorithm
@@ -56,25 +56,21 @@ additional pods become ready, or pods enter a non-ready state.
 
       * Use the Helm chart [ingress-per-domain](https://github.com/oracle/weblogic-kubernetes-operator/blob/main/kubernetes/samples/charts/ingress-per-domain).  
 
-        Each ingress provider supports a number of 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.
+        Each ingress provider supports a number of annotations in Ingress resources. This Helm chart allows you to define the routing rules without dealing with the detailed provider-specific annotations.
 
      * Create the Ingress resource manually from a YAML file.  
 
         Manually create an Ingress YAML file and then apply it to the Kubernetes cluster.
 
-#### Guide and samples for Traefik, Voyager/HAProxy, and NGINX
+#### Guide and samples for Traefik and NGINX
 
 Information about how to install and configure these ingress controllers to load balance WebLogic clusters is provided here:
 
  - [Traefik guide](https://github.com/oracle/weblogic-kubernetes-operator/blob/main/kubernetes/samples/charts/traefik/README.md)
- - [Voyager guide](https://github.com/oracle/weblogic-kubernetes-operator/blob/main/kubernetes/samples/charts/voyager/README.md)
  - [NGINX guide](https://github.com/oracle/weblogic-kubernetes-operator/blob/main/kubernetes/samples/charts/nginx/README.md)
 
  {{% notice note %}}
- For production environments, we recommend NGINX, Voyager, Traefik (2.2.1 or later) ingress controllers, Apache, or the load balancer provided by your cloud provider.
+ For production environments, we recommend NGINX, Traefik (2.2.1 or later) ingress controllers, Apache, or the load balancer provided by your cloud provider.
  {{% /notice %}}
 
-Samples are also provided for these two ingress controllers, showing how to manage multiple WebLogic clusters as the backends, using different routing rules, host-routing and path-routing; and TLS termination:
-
-- [Traefik samples](https://github.com/oracle/weblogic-kubernetes-operator/blob/main/kubernetes/samples/charts/traefik/samples)
-- [Voyager samples](https://github.com/oracle/weblogic-kubernetes-operator/blob/main/kubernetes/samples/charts/voyager/samples)
+Samples are also provided for the Traefik ingress controller, showing how to manage multiple WebLogic clusters as the backends, using different routing rules, host-routing and path-routing; and TLS termination: [Traefik samples](https://github.com/oracle/weblogic-kubernetes-operator/blob/main/kubernetes/samples/charts/traefik/samples).

kubernetes/hands-on-lab/tutorials/install.traefik.ocishell.md

@@ -2,7 +2,7 @@
 
 ### Install and configure Traefik  ###
 
-The WebLogic Kubernetes Operator supports three load balancers or ingress controllers: Traefik, Voyager, and Apache. Samples are provided in the [documentation](https://github.com/oracle/weblogic-kubernetes-operator/blob/v2.5.0/kubernetes/samples/charts/README.md).
+The WebLogic Kubernetes Operator supports three load balancers or ingress controllers: Traefik, NGINX, and Apache. Samples are provided in the [documentation](https://github.com/oracle/weblogic-kubernetes-operator/blob/v2.5.0/kubernetes/samples/charts/README.md).
 
 This tutorial demonstrates how to install the [Traefik](https://traefik.io/) ingress controller to provide load balancing for WebLogic Server clusters.
 

kubernetes/samples/README.md

@@ -21,6 +21,5 @@ While these samples may be useful and usable as is, it is intended that you woul
 ## Sample Helm charts
 
 * [Sample Traefik Helm chart](charts/traefik/README.md) for setting up a Traefik load balancer for WebLogic clusters.
-* [Sample Voyager Helm chart](charts/voyager/README.md) for setting up a Voyager load balancer for WebLogic clusters.
-* [Sample Ingress Helm chart](charts/ingress-per-domain/README.md) for setting up a Kubernetes Ingress for each WebLogic cluster using a Traefik or Voyager load balancer.
+* [Sample Ingress Helm chart](charts/ingress-per-domain/README.md) for setting up a Kubernetes Ingress for each WebLogic cluster using a Traefik or NGINX load balancer.
 * [Sample Apache  Helm chart](charts/apache-webtier/README.md) and [Apache samples using the default or custom configurations](charts/apache-samples/README.md) for setting up a load balancer for WebLogic clusters using the Apache HTTP Server with WebLogic Server Plugins.

kubernetes/samples/charts/README.md

@@ -2,10 +2,9 @@
 
 ## Load balancer sample scripts
 
-The WebLogic Kubernetes Operator supports three load balancers: Traefik, Voyager, and Apache. We provide samples that demonstrate how to install and configure each one. The samples are located in following folders:
+The WebLogic Kubernetes Operator supports three load balancers: Traefik, NGINX, and Apache. We provide samples that demonstrate how to install and configure each one. The samples are located in following folders:
 
 * [traefik](traefik/README.md)
-* [voyager](voyager/README.md)
 * [NGINX](nginx/README.md)
 * apache-samples/[custom-sample](apache-samples/custom-sample/README.md)
 * apache-samples/[default-sample](apache-samples/default-sample/README.md)

kubernetes/samples/charts/ingress-per-domain/README.md

@@ -1,10 +1,10 @@
 # An ingress per domain chart
-This chart is for deploying an Ingress resource in front of a WebLogic domain cluster. We support ingress types: Traefik, Voyager, and NGINX.
+This chart is for deploying an Ingress resource in front of a WebLogic domain cluster. We support ingress types: Traefik and NGINX.
 
 ## Prerequisites
 - Have Docker and a Kubernetes cluster running and have `kubectl` installed and configured.
 - Have Helm installed.
-- The corresponding ingress controller, Traefik, Voyager, or NGINX, is installed in the Kubernetes cluster.
+- The corresponding ingress controller, Traefik or NGINX, is installed in the Kubernetes cluster.
 - A WebLogic domain cluster deployed by `weblogic-operator` is running in the Kubernetes cluster.
 
 ## Installing the chart
@@ -35,24 +35,6 @@ traefik:
   hostname: domain1.org
 ```
 
-Sample `values.yaml` file for the Voyager Ingress:
-```yaml
-type: VOYAGER
-
-# WLS domain as backend to the load balancer
-wlsDomain:
-  domainUID: domain1
-  clusterName: cluster1  
-  managedServerPort: 8001
-
-# Voyager specific values
-voyager:
-  # web port
-  webPort: 30305
-  # stats port
-  statsPort: 30315
-```
-
 Sample `values.yaml` file for the NGINX Ingress:
 ```yaml
 type: NGINX
@@ -85,7 +67,5 @@ The following table lists the configurable parameters of this chart and their de
 | `wlsDomain.managedServerPort` | Port number of the managed servers in the WLS domain cluster. | `8001` |
 | `traefik.hostname` | Hostname to route to the WLS domain cluster. | `domain1.org` |
 | `nginx.hostname` | Hostname to route to the WLS domain cluster. | `domain1.org` |
-| `voyager.webPort` | Web port to access the Voyager load balancer. | `30305` |
-| `voyager.statsPort` | Port to access the Voyager/HAProxy stats page. | `30315` |
 
 **Note:** The input values `domainUID` and `clusterName` will be used to generate the Kubernetes `serviceName` of the WLS cluster with the format `domainUID-cluster-clusterName`.

kubernetes/samples/charts/ingress-per-domain/values.yaml

@@ -5,7 +5,7 @@
 # This is a YAML-formatted file.
 # Declare variables to be passed into your templates.
 
-# Load balancer type.  Supported values are: TRAEFIK, VOYAGER
+# Load balancer type.  Supported values are: TRAEFIK, NGINX
 type: TRAEFIK
 
 # WLS domain as backend to the load balancer
@@ -19,12 +19,6 @@ traefik:
   # hostname used by host-routing
   hostname: domain1.org
 
-# Voyager specific values
-voyager:
-  # web port
-  webPort: 30305
-  # stats port
-  statsPort: 30315
 
 # NGINX specific values
 nginx: