Update README to document one-command installation

Author: jfrancoa

README.md

@@ -39,13 +39,21 @@ The Weaviate Operator wraps the [weaviate-helm](https://github.com/weaviate/weav
 
 There are multiple ways to run the operator:
 
-1. Run the operator locally outside the cluster by executing the following command:
+1. The easiest way is to run the one-command Manifest:
+
+```shell
+kubectl apply -f https://github.com/weaviate/weaviate-operator/releases/download/0.0.1/operator.yaml
+```
+
+Other alternative ways to install it is:
+
+1. Run the operator locally outside the cluster by executing the following command inside the `weaviate-operator` repository:
 
 ```shell
 make install run
 ```
 
-2. Run the operator as a Deployment inside the cluster by executing the following command:
+2. Run the operator as a Deployment inside the cluster by executing the following command inside the `weaviate-operator` repository:
 
 ```shell
 make deploy
@@ -75,13 +83,19 @@ To create the Weaviate CR, apply the modified `config/samples/apps_v1alpha1_weav
 kubectl apply -f config/samples/apps_v1alpha1_weaviatecluster.yaml -n weaviate
 ```
 
+make sure to create the namespace `weaviate` (or any other namespace in which you want you Weaviate nodes to run) in advance:
+
+```shell
+kubectl create ns weaviate
+```
+
 or simply create your own definition of the WeaviateCluster (based on the [weaviate-helm values.yaml](https://github.com/weaviate/weaviate-helm/blob/master/weaviate/values.yaml)):
 
 ```
 apiVersion: apps.weaviate.io/v1alpha1
  kind: WeaviateCluster
  metadata:
-   name: weaviate_test_cluster
+   name: weaviatecluster-sample
    namespace: weaviate
  spec:
    # Default values copied from <project_dir>/helm-charts/weaviate/values.yaml
@@ -101,9 +115,22 @@ apiVersion: apps.weaviate.io/v1alpha1
    storage:
      size: 32Gi
 ```
+A new custom resource `weaviatecluster` will be now available:
+
+```shell
+kubectl get weaviatecluster -n weaviate
+NAME                     AGE
+weaviatecluster-sample   13s
 
+```
 The operator will create the statefulset for the CR based on the specified replica count and other configurations. Keep in mind that the resources will be created in the namespace you decide, in this example the `weaviate` namespace is used, but you can install it in any other namespace. 
 
+```shell
+kubectl get statefulset weaviate -n weaviate
+NAME       READY   AGE
+weaviate   3/3     65s
+```
+
 ## Troubleshooting
 
 If you encounter any issues, you can check the operator logs using the following command:
@@ -120,11 +147,28 @@ kubectl describe weaviateclusters.apps.weaviate.io -n weaviate
 
 ## Cleanup
 
-To clean up the resources, delete the custom resource using the following command:
+To clean up the `weaviatecluster` resources, delete the custom resource using the following command:
 
 ```shell
 kubectl delete -f config/samples/apps_v1alpha1_weaviatecluster.yaml -n weaviate
 ```
+or deleting it directly:
+
+```shell
+kubectl delete weaviatecluster weaviatecluster-sample -n weaviate
+```
+
+Then, uninstall the operator either using the single-command manifest:
+
+```shell
+kubectl delete -f https://github.com/weaviate/weaviate-operator/releases/download/0.0.1/operator.yaml
+```
+
+or using the repo's Makefile, by running the following command inside the `weaviate-operator` repo:
+
+```shell
+make undeploy
+```
 
-Then, undeploy the operator using the `make undeploy` command or simply stop the process if you started it via `make install run`.
+or simply stop the process if you started it via `make install run`.