doc: new install should already use the generated crd yaml

doc/user/install_guide.md

@@ -16,20 +16,20 @@ Set up basic service account for etcd operator:
 $ kubectl create -f example/serviceaccount.yaml
 ```
 
-## Install etcd operator
+## Set up CRDs
 
-Create a deployment for etcd operator:
+Set up custom resource definitions for the etcd operator
 
 ```bash
-$ kubectl create -f example/deployment.yaml
+$ kubectl create -f example/crd/etcd.database.coreos.com_etcdclusters.yaml
 ```
 
-etcd operator will automatically create a Kubernetes Custom Resource Definition (CRD):
+## Install etcd operator
+
+Create a deployment for etcd operator:
 
 ```bash
-$ kubectl get customresourcedefinitions
-NAME                                    KIND
-etcdclusters.etcd.database.coreos.com   CustomResourceDefinition.v1beta1.apiextensions.k8s.io
+$ kubectl create -f example/deployment.yaml
 ```
 
 ## Uninstall etcd operator
@@ -45,8 +45,7 @@ Clean up etcd operator:
 ```bash
 kubectl delete -f example/deployment.yaml
 kubectl delete -f example/serviceaccount.yaml
-kubectl delete endpoints etcd-operator
-kubectl delete crd etcdclusters.etcd.database.coreos.com
+kubectl delete -f example/crd/etcd.database.coreos.com_etcdclusters.yaml
 kubectl delete clusterrole etcd-operator
 kubectl delete clusterrolebinding etcd-operator
 ```

doc/user/rbac.md

@@ -15,6 +15,7 @@ The permission model required for the etcd operator depends on the value of its
   - In this mode the operator requires a ClusterRole with the permission to create a CRD.
 - `--create-crd=false` Creates a CR without first creating a CRD.
   - In this mode the operator can be run with just a Role without the permission to create a CRD.
+  - Make sure to apply the crd in `example/crd`
 
 ## Set up RBAC