Fixed Curator integration.

Author: pires

README.md

@@ -233,24 +233,32 @@ You should see something similar to the following:
 
 ## Clean up with Curator
 
-Additionally, you can run a Scheduled Job running [Curator](https://github.com/elastic/curator) to clean up your indices (or do other actions on your ES).
-
-For this you need to deploy a Config Map (which configures the Curator) and the Scheduled Job:
+Additionally, you can run a [CronJob](http://kubernetes.io/docs/user-guide/cron-jobs/) that will periodically run [Curator](https://github.com/elastic/curator) to clean up your indices (or do other actions on your cluster).
 
 ```
-kubectl create -f es-curator-configmap.yaml
+kubectl create -f es-curator-config.yaml
 kubectl create -f es-curator.yaml
 ```
 
-The pod is set to run once a day at 1 minute past midnight and delete indices that are older than 3 days.
+Please, confirm the job has been created.
+
+```
+$ kubectl get cronjobs
+NAME      SCHEDULE    SUSPEND   ACTIVE    LAST-SCHEDULE
+curator   1 0 * * *   False     0         <none>
+```
+
+The job is configured to run once a day at _1 minute past midnight and delete indices that are older than 3 days_.
 
-You can change the schedule by editing the Cron notation in the `es-curator.yaml`.
+**Notes**
 
-You can change the action (e.g. delete older than 3 days) by editing the `es-curator-configmap.yaml`. The definition of the `action_file.yaml` is quite self-explaining for simple set ups. For more advanced configuration options, please consult the [Curator Documentation](https://www.elastic.co/guide/en/elasticsearch/client/curator/current/index.html).
+- You can change the schedule by editing the cron notation in `es-curator.yaml`.
+- You can change the action (e.g. delete older than 3 days) by editing the `es-curator-config.yaml`.
+- The definition of the `action_file.yaml` is quite self-explaining for simple set-ups. For more advanced configuration options, please consult the [Curator Documentation](https://www.elastic.co/guide/en/elasticsearch/client/curator/current/index.html).
 
-If you want to remove Curator again, just run:
+If you want to remove the curator job, just run:
 
 ```
-kubectl delete scheduledjob curator
+kubectl delete cronjob curator
 kubectl delete configmap curator-config
 ``` 

es-curator-config.yaml

@@ -2,7 +2,6 @@ apiVersion: v1
 kind: ConfigMap
 metadata:
   name: curator-config
-  namespace: logging
 data:
   action_file.yml: |-
     ---

es-curator.yaml

@@ -1,5 +1,5 @@
 apiVersion: batch/v2alpha1
-kind: ScheduledJob
+kind: CronJob
 metadata:
   name: curator
 spec: