doc updates

Author: markxnelson

README.md

@@ -100,7 +100,6 @@ If you would rather see the developers demonstrating the operator rather than re
 * [Deploying a web application, scaling a WebLogic cluster with the operator and verifying load balancing](https://youtu.be/hx4OPhNFNDM)
 * [Using WLST against a domain running in Kubernetes](https://youtu.be/eY-KXEk8rI4) shows how to create a data source for an Oracle database that is also running in Kubernetes.
 * [Scaling a WebLogic cluster with WLDF](https://youtu.be/Q8iZi2e9HvU)
-* [Prometheus integration](https://youtu.be/D7KWVXzzqx8) including exporting WebLogic Server metrics to Prometheus and creating a Prometheus alert to trigger scaling
 * watch this space, more to come!
 
 Like what you see?  Read on for all the nitty-gritty details...
@@ -134,10 +133,6 @@ Please refer to [Creating a WebLogic domain with the operator](site/creating-dom
 
 [comment]: # ( Manually creating a WebLogic domain.  If preferred, a domain can be created manually, i.e. without using the scripts provided with the operator.  As long as the domain follows the guidelines, it can still be managed by the operator.  Please refer to [Manually creating a WebLogic domain] site/manually-creating-domain.md for details.  A good example of when manual domain creation may be preferred is when a user already has a set of existing WLST scripts that are used to create domains and they wish to reuse those same WLST scripts in Kubernetes, perhaps with some small modifications. )
 
-## Exporting WebLogic metrics to Prometheus
-
-When using the operator to manage WebLogic domains, it may also be desirable to export WebLogic Server metrics to Prometheus using the [WLS Exporter](https://github.com/oracle/weblogic-monitoring-exporter), which allows metrics to be displayed in Grafana, and permits the creation of alerts and initiation of scaling actions from Prometheus alerts.  Please refer to [Prometheus integration](site/prometheus.md) for more information.
-
 ## Starting up the domain
 
 The operator will automatically start up domains that it is aware of, based on the configuration in the domain custom resource.  Please refer to [Startup up a WebLogic domain](site/starting-domain.md) for details.
@@ -181,8 +176,6 @@ Find the names of the persistent volume claim and the persistent volume in the d
 
 To permanently delete the actual domain configuration, delete the physical volume using the appropriate tools.  For example, if the persistent volume used the `HostPath provider`, then delete the corresponding directory on the Kubernetes master.
 
-Be aware that there may be metric data from the domain in Prometheus if this option was used.  These data will need to be deleted separately, if desired.
-
 ## Removing the operator
 
 To remove the operator from a Kubernetes cluster, issue the following commands:

site/architecture.md

@@ -7,7 +7,7 @@ The operator consists of the following two main parts:
 
 The operator is packaged in a Docker image `container-registry.oracle.com/middleware/weblogic-operator:latest`.  This image can be deployed to a Kubernetes cluster.  It is recommended that the operator be deployed in its own namespace.  Only one operator is permitted in a namespace; however, multiple operators may be deployed in a Kubernetes cluster provided they are each in their own namespace and the list of namespaces they manage do not overlap.
 
-Scripts are provided to deploy the operator to a Kubernetes cluster.  These scripts also provide options to install and configure a load balancer, ELK integration and Prometheus integration.
+Scripts are provided to deploy the operator to a Kubernetes cluster.  These scripts also provide options to install and configure a load balancer and ELK integration.
 
 The operator registers a Kubernetes custom resource definition called `domain.weblogic.oracle` (shortname `domain`, plural `domains`).  
 
@@ -20,7 +20,6 @@ The Kubernetes cluster has several namespaces.  Components may be deployed into
 *	The operator is deployed into its own namespace.  If the ELK integration option is configured, then a logstash pod will also be deployed in the operator’s namespace.
 *	WebLogic domains will be deployed into various namespaces.  There can be more than one domain in a namespace if desired.  There is no limit on the number of domains or namespaces that an operator can manage.  Note that there can be more than one operator in a Kubernetes cluster, but each operator is configured with a list of the specific namespaces that it is responsible for.  The operator will not take any action on any domain that is not in one of the namespaces the operator is configured to manage.
 *	If the ELK integration option is configured, ElasticSearch and Kibana will be deployed in the `default` namespace.
-*	If the Prometheus integration option is configured, Prometheus and Grafana will be deployed in the `monitoring` namespace.
 *	If a load balancer is configured, it will be deployed in the `kube-system` namespace.
 
 ## Domain architecture

site/creating-domain.md

@@ -115,7 +115,6 @@ The following parameters must be provided in the input file:
 | loadBalancerAdminPort	| The node port for the load balancer to accept admin requests.	| 30315 |
 | loadBalancerWebPort	| The node port for the load balancer to accept user traffic. 	| 30305 |
 | enableLoadBalancerAdminPort	| Determines whether the load balancer administration port should be exposed outside the Kubernetes cluster.	| false |
-| enablePrometheusIntegration	| Determines whether the Prometheus integration will be enabled.  If set to ‘true’, then the WebLogic Monitoring Exporter will be installed on all servers in the domain and configured to export metrics to Prometheus. |	false |
 
 ## Limitations of the create domain script
 

site/installation.md

@@ -100,8 +100,6 @@ The operator can install the ELK stack and publish its logs into ELK.  If enable
 
 To enable the ELK integration, set the `enableELKintegration` option to `true`.
 
-[comment]: # ( Metrics integration with Prometheus - Write me )
-
 ## Deploying the operator to a Kubernetes cluster
 
 To deploy the operator, run the deployment script and give it the location of your inputs file:

site/prometheus.md

@@ -1,6 +1,6 @@
 # Scaling a WebLogic cluster
 
-Explain how the scaling works – replicas, etc., the REST endpoint.
+The operator provides the ability to scale WebLogic clusters by simply editing the replicas setting, as you would do with most other Kubernetes resources that support scaling.
 
 ## Initiating a scaling operation using the REST API
 
@@ -50,13 +50,3 @@ When the operator receives a scaling request, it will:
   *	at the domain level, if not defined in a `clusterStartup` entry and the `startupControl` property is set to `AUTO`.
 
 In response to a change to either `replicas` property, in the domain custom resource, the operator will increase or decrease the number of pods (Managed Servers) to match the desired replica count.
-
-## Initiating a scaling operation from WLDF
-
-Note that there is a video demonstration of scaling with WLDF available [here](https://youtu.be/Q8iZi2e9HvU).
-
-Write me
-
-## Initiating a scaling operation from Prometheus
-
-Write me