Remove instructions for manually installing the operator since helm must now be used. (#696)

Author: moreaut

site/developer.md

@@ -68,6 +68,8 @@ The Javadoc is also available in the GitHub repository [here](https://oracle.git
 
 ## Running integration tests
 
+TODO - I think this entire section needs a redo.  Also, helm must be used to install the operator - heml-charts.md (v.s. manual-installation.md)
+
 The project includes integration tests that can be run against a Kubernetes cluster.  If you want to use these tests, you will need to provide your own Kubernetes cluster.  You will need to obtain the `kube.config` file for an administrator user and make it available on the machine running the build.  Tests will run against Kubernetes 1.10.11+, 1.11.5+, and 1.12.3+.
 
 To run the tests, uncomment the following `execution` element in the `pom.xml` file and update the `KUBECONFIG` to point to your kube config file.

site/install.md

@@ -4,14 +4,9 @@ An operator is an application-specific controller that extends Kubernetes to cre
 of complex applications. The Oracle WebLogic Server Kubernetes Operator follows the standard Kubernetes operator pattern, and 
 simplifies the management and operation of WebLogic domains and deployments. 
 
-
 You can have one or more operators in your Kubernetes cluster that manage one or more WebLogic domains each. 
-We provide a Helm chart to manage the installation and configuration of the operator and that is the 
-*preferred method* of managing operators.  Detailed instructions are available [here](helm-charts.md).
-
-If, for some reason, you do not want to use Helm, it is still possible to perform a manual 
-installation of the operator.  This is *not the recommended approach*, but is fully [documented here](manual-installation.md)
-if you wish to use this approach.
+We provide a Helm chart to manage the installation and configuration of the operator.
+Detailed instructions are available [here](helm-charts.md).
 
 ## Operator Docker image