update Traefik/Voyager doc (#627)

* update chart readmes

* add ingress.md

* Update ingress.md

* Update quickstart.md

* Update ingress.md

* Update ingress.md

Author: Lily He

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

@@ -13,7 +13,7 @@ To install the chart with the release name, `my-ingress`, with the given `values
 ```
 # Change directory to the cloned git weblogic-kubernetes-operator repo.
 $ cd kubernetes/samples/charts
-$ helm install ingress-per-domain --name my-ingress --value values.yaml
+$ helm install ingress-per-domain --name my-ingress --values values.yaml
 ```
 The Ingress resource will be created in the same namespace as the WebLogic domain cluster.
 

kubernetes/samples/charts/traefik/README.md

@@ -1,7 +1,7 @@
 # Install and configure Traefik
 ## Install the Traefik operator with a Helm chart
 The Traefik Helm chart is located in the official Helm project `charts` directory at https://github.com/helm/charts/tree/master/stable/traefik.
-The chart is in the default repository for Helm at https://kubernetes-charts.storage.googleapis.com/ and is installed by default.
+The chart is in the default repository for Helm.
 
 To install the Traefik operator in the `traefik` namespace with default settings:
 ```
@@ -22,6 +22,12 @@ If you want, you can download the Traefik Helm chart and untar it into a local f
 $ helm fetch  stable/traefik --untar
 ```
 
+## Update the Traefik operator
+After the Traefik operator is installed and running, if you want to change some configurations of the operator, use `helm upgrade` to achieve this.
+```
+$ helm upgrade traefik-operator stable/traefik --values values.yaml 
+```
+
 ## Configure Traefik as a load balancer for WLS domains
 In this section we'll demonstrate how to use Traefik to handle traffic to backend WLS domains.
 
@@ -40,17 +46,17 @@ $ kubectl create -f samples/host-routing.yaml
 ```
 Now you can send requests to different WLS domains with the unique entry point of Traefik with different hostnames.
 ```
-$ curl --silent -H 'host: domain1.org' http://${HOSTNAME}:30305/testwebapp/
-$ curl --silent -H 'host: domain2.org' http://${HOSTNAME}:30305/testwebapp/
+$ curl -H 'host: domain1.org' http://${HOSTNAME}:30305/testwebapp/
+$ curl -H 'host: domain2.org' http://${HOSTNAME}:30305/testwebapp/
 ```
 #### Install a path-routing Ingress
 ```
 $ kubectl create -f samples/path-routing.yaml
 ```
 Now you can send requests to different WLS domains with the unique entry point of Traefik with different paths.
 ```
-$ curl --silent http://${HOSTNAME}:30305/domain1/
-$ curl --silent http://${HOSTNAME}:30305/domain2/
+$ curl http://${HOSTNAME}:30305/domain1/
+$ curl http://${HOSTNAME}:30305/domain2/
 ```
 #### Install a TLS-enabled Ingress
 This sample demonstrates accessing the two WLS domains using an HTTPS endpoint and the WLS domains are protected by different TLS certificates.

kubernetes/samples/charts/voyager/README.md

@@ -37,6 +37,12 @@ If you want, you can download the Voyager Helm chart and untar it into a local f
 $ helm fetch appscode/voyager --untar --version 7.4.0
 ```
 
+## Update the Voyager operator
+After the Voyager operator is installed and running, if you want to change some configurations of the operator, use `helm upgrade` to achieve this.
+```
+$ helm upgrade voyager-operator appscode/voyager [flags]
+```
+
 ## Configure Voyager as a load balancer for WLS domains
 We'll demonstrate how to use Voyager to handle traffic to backend WLS domains.
 
@@ -55,8 +61,8 @@ $ kubectl create -f samples/host-routing.yaml
 ```
 Now you can send requests to different WLS domains with the unique entry point of Voyager with different hostnames.
 ```
-$ curl --silent -H 'host: domain1.org' http://${HOSTNAME}:30305/testwebapp/
-$ curl --silent -H 'host: domain2.org' http://${HOSTNAME}:30305/testwebapp/
+$ curl -H 'host: domain1.org' http://${HOSTNAME}:30305/testwebapp/
+$ curl -H 'host: domain2.org' http://${HOSTNAME}:30305/testwebapp/
 ```
 To see the Voyager host-routing stats web page, access the URL `http://${HOSTNAME}:30315` in your web browser.
 

site/ingress.md

@@ -0,0 +1,41 @@
+# Load balancing with Ingress
+Ingress is a approach provided by k8s to hook up and run a load balancer. Pls see detail in [the Ingress doc](https://kubernetes.io/docs/concepts/services-networking/ingress/).  
+
+## WebLogic domains as backends of Ingress
+
+In Ingress a backend is defined as [a k8s service](https://kubernetes.io/docs/concepts/services-networking/service/), more specifically, a combination of a `serviceName` and a `servicePort`. A WebLogic domain is a backend of the load balancer. When the WebLogic operator creates a WebLogic domain, it always creates a k8s service for each WebLogic cluster in the domain. With the proper label selector defined in the generated service, the service contains all-and-only the running WebLogic server pods within the WebLogic cluster.
+
+The name of the k8s service generated for a WebLogic cluster follows the pattern '<domainUID>-cluster-<clusterName>'. For instance, if the doaminUID is 'domain1' and the cluster name is 'cluster-1', the corresponding k8s service name generated by WebLogic operator will be 'domain1-cluster-cluster-1'. 
+
+The service name has the following limitation in k8s:
+> A DNS-1035 label must consist of lower case alphanumeric characters or '-', start with an alphabetic character, and end with an alphanumeric character (e.g. 'my-name',  or 'abc-123', regex used for validation is '[a-z]([-a-z0-9]*[a-z0-9])?').
+
+To meet the limitation, if the domainUID or the cluster name contains some upper-case characters or  `_` , in the generated service name the upper-case characters will be converted to lower-case and `_` will be converted to `-` . For instance, if the doaminUID is 'myDomain_1' and the cluster name is 'myCluster_1', the corresponding k8s service name generated by WebLogic operator will be  'mydomain-1-cluster-mycluster-1'. 
+
+The service, `serviceName` and `servicePort`, of a WebLogic cluster will be used in the routing rules defined in Ingress resources and the load balancer will route traffic to the WebLogic servers within the cluster based on the rules. Note that eac traffic load, redirected by the load balancer, is not sent to the service directly, but instead, to one endpoint of the service based on its load-balancing algorithm. The load balancer depends on the k8s platform to maintain the live endpoint list of the service.
+
+## Steps to setup an Ingress load balancer
+
+1. Install the Ingress controller.  
+After the Ingress controller is running, it monitors Ingress resources in given namespace(s) and acts accordingly.
+
+1. Install Ingress Resource(s)  
+Ingress resources contain routing rules to one or more backends. And Ingress controller is responsible to apply the rules to the underline load balancer.  
+There are two approaches to create the Ingress resource:  
+   1. Use the helm chart [ingress-per-domain](kubernetes/samples/charts/ingress-per-domain).  
+   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.  
+
+   1. Create and install the Ingress yaml manually.  
+   Manually edit the Ingress yaml file and then install it to the k8s cluster. 
+
+## Guide and samples for Traefik and Voyager/HAProxy
+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).
+ - [Treafik guide](kubernetes/samples/charts/traefik/README.md)
+ - [Voyager guide](kubernetes/samples/charts/voyager/README.md)
+
+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.
+- [Treafik samples](kubernetes/samples/charts/traefik/samples)
+- [Voyager samples](kubernetes/samples/charts/voyager/samples)
+
+
+

site/quickstart.md

@@ -96,7 +96,7 @@ $ helm update kubernetes/charts/weblogic-operator --name my-operator --namespace
 
 ```
 $ cd kubernetes/samples/charts
-$ helm install ingress-per-domain --name domain1-ingress --value values.yaml
+$ helm install ingress-per-domain --name domain1-ingress --values values.yaml
 ```
 
 (At this point, do they have a WebLogic Kubernetes deployment in a Kubernetes cluster? If so, we have to give them something to look at, to verify their results.)