remove Tiller (#1958)

* remove Tiller

* add back command

Author: rosemarymarano

docs-source/content/quickstart/prerequisites.md

@@ -7,7 +7,7 @@ weight: 2
 
 For this exercise, you’ll need a Kubernetes cluster. If you need help setting one up, check out our [cheat sheet]({{< relref "/userguide/overview/k8s-setup#cheat-sheet-for-setting-up-kubernetes" >}}). This guide assumes a single node cluster.
 
-The operator uses Helm to create and deploy the necessary resources and then run the operator in a Kubernetes cluster. For Helm installation and usage information, see [Install Helm and Tiller]({{< relref "/userguide/managing-operators/_index.md#install-helm-and-tiller" >}}).
+The operator uses Helm to create and deploy the necessary resources and then run the operator in a Kubernetes cluster. For Helm installation and usage information, see [Install Helm]({{< relref "/userguide/managing-operators/_index.md#install-helm" >}}).
 
 You should clone this repository to your local machine so that you have access to the
 various sample files mentioned throughout this guide:

docs-source/content/security/service-accounts.md

@@ -33,5 +33,5 @@ look for the `serviceAccount` value using the Helm command:
 $ helm get values --all weblogic-operator
 ```
 #### Additional reading
-* [Helm service account]({{<relref "userguide/managing-operators/_index.md#install-helm-and-tiller">}})
+* [Helm service account]({{<relref "userguide/managing-operators/_index.md#install-helm">}})
 * [Operator Helm chart service account configuration]({{<relref "/userguide/managing-operators/using-the-operator/using-helm/_index.md#serviceaccount">}})

docs-source/content/userguide/managing-operators/_index.md

@@ -23,35 +23,9 @@ the API version in the data (weblogic.oracle/v2) does not match the expected API
 ```
 {{% /notice %}}      
 
-#### Install Helm and Tiller
+### Install Helm
 
-Helm has two parts: a client (Helm) and a server (Tiller). Tiller runs inside of your Kubernetes cluster, and manages releases (installations) of your charts. For detailed instructions on installing Helm and Tiller, see https://github.com/helm/helm.
-
-In order to use Helm to install and manage the operator, you need to ensure that the service account that Tiller uses
-has the `cluster-admin` role.  The default would be `default` in namespace `kube-system`.  You can give that service
-account the necessary permissions with this command:
-
-```
-cat << EOF | kubectl apply -f -
-apiVersion: rbac.authorization.k8s.io/v1
-kind: ClusterRoleBinding
-metadata:
-  name: helm-user-cluster-admin-role
-roleRef:
-  apiGroup: rbac.authorization.k8s.io
-  kind: ClusterRole
-  name: cluster-admin
-subjects:
-- kind: ServiceAccount
-  name: default
-  namespace: kube-system
-EOF
-```
-
-{{% notice note %}}
-Oracle strongly recommends that you create a new service account to be used exclusively by Tiller and grant
-`cluster-admin` to that service account, rather than using the `default` one.
-{{% /notice %}}
+Helm manages releases (installations) of your charts. For detailed instructions on installing Helm, see https://github.com/helm/helm.
 
 ### Operator's Helm Chart Configuration
 

docs-source/content/userguide/managing-operators/using-the-operator/using-helm.md

@@ -491,12 +491,6 @@ Error: UPGRADE FAILED: Service "external-weblogic-operator-svc" is invalid: spec
 The `helm install` eventually times out and creates a failed release.
 ```
 $ helm install kubernetes/charts/weblogic-operator --name op2 --namespace myuser-op2-ns --values o24.yaml --wait --no-hooks
-Error: release op2 failed: timed out waiting for the condition
-
-kubectl logs -n kube-system tiller-deploy-f9b8476d-mht6v
-...
-[kube] 2018/12/06 21:16:54 Deployment is not ready: myuser-op2-ns/weblogic-operator
-...
 ```
 
 To recover: