Bump Version to 0.0.8

* Add doc how to verify reloader working

* fix the text

.version

@@ -1 +1 @@
-0.0.7
+0.0.8

deployments/kubernetes/chart/reloader/Chart.yaml

@@ -3,7 +3,7 @@
 apiVersion: v1
 name: reloader
 description: Reloader chart that runs on kubernetes
-version: 0.0.7
+version: 0.0.8
 keywords:
   - Reloader
   - kubernetes

deployments/kubernetes/chart/reloader/values.yaml

@@ -7,9 +7,9 @@ reloader:
   labels:
     provider: stakater
     group: com.stakater.platform
-    version: 0.0.7
+    version: 0.0.8
   image:
     name: stakater/reloader
-    tag: "0.0.7"
+    tag: "0.0.8"
     pullPolicy: IfNotPresent
   watchGlobally: true

deployments/kubernetes/manifests/deployment.yaml

@@ -7,8 +7,8 @@ metadata:
     app: reloader
     group: com.stakater.platform
     provider: stakater
-    version: 0.0.7
-    chart: "reloader-0.0.7"
+    version: 0.0.8
+    chart: "reloader-0.0.8"
     release: "RELEASE-NAME"
     heritage: "Tiller"
   name: reloader
@@ -29,7 +29,7 @@ spec:
     spec:
       containers:
       - env:
-        image: "stakater/reloader:0.0.7"
+        image: "stakater/reloader:0.0.8"
         imagePullPolicy: IfNotPresent
         name: reloader
       serviceAccountName: reloader

deployments/kubernetes/manifests/rbac.yaml

@@ -7,8 +7,8 @@ metadata:
     app: reloader
     group: com.stakater.platform
     provider: stakater
-    version: 0.0.7
-    chart: "reloader-0.0.7"
+    version: 0.0.8
+    chart: "reloader-0.0.8"
     release: "RELEASE-NAME"
     heritage: "Tiller"
   name: reloader
@@ -20,8 +20,8 @@ metadata:
     app: reloader
     group: com.stakater.platform
     provider: stakater
-    version: 0.0.7
-    chart: "reloader-0.0.7"
+    version: 0.0.8
+    chart: "reloader-0.0.8"
     release: "RELEASE-NAME"
     heritage: "Tiller"
   name: reloader-role
@@ -57,8 +57,8 @@ metadata:
     app: reloader
     group: com.stakater.platform
     provider: stakater
-    version: 0.0.7
-    chart: "reloader-0.0.7"
+    version: 0.0.8
+    chart: "reloader-0.0.8"
     release: "RELEASE-NAME"
     heritage: "Tiller"
   name: reloader-role-binding

deployments/kubernetes/reloader.yaml

@@ -7,8 +7,8 @@ metadata:
     app: reloader
     group: com.stakater.platform
     provider: stakater
-    version: 0.0.7
-    chart: "reloader-0.0.7"
+    version: 0.0.8
+    chart: "reloader-0.0.8"
     release: "RELEASE-NAME"
     heritage: "Tiller"
   name: reloader
@@ -29,7 +29,7 @@ spec:
     spec:
       containers:
       - env:
-        image: "stakater/reloader:0.0.7"
+        image: "stakater/reloader:0.0.8"
         imagePullPolicy: IfNotPresent
         name: reloader
       serviceAccountName: reloader
@@ -43,8 +43,8 @@ metadata:
     app: reloader
     group: com.stakater.platform
     provider: stakater
-    version: 0.0.7
-    chart: "reloader-0.0.7"
+    version: 0.0.8
+    chart: "reloader-0.0.8"
     release: "RELEASE-NAME"
     heritage: "Tiller"
   name: reloader
@@ -56,8 +56,8 @@ metadata:
     app: reloader
     group: com.stakater.platform
     provider: stakater
-    version: 0.0.7
-    chart: "reloader-0.0.7"
+    version: 0.0.8
+    chart: "reloader-0.0.8"
     release: "RELEASE-NAME"
     heritage: "Tiller"
   name: reloader-role
@@ -93,8 +93,8 @@ metadata:
     app: reloader
     group: com.stakater.platform
     provider: stakater
-    version: 0.0.7
-    chart: "reloader-0.0.7"
+    version: 0.0.8
+    chart: "reloader-0.0.8"
     release: "RELEASE-NAME"
     heritage: "Tiller"
   name: reloader-role-binding

docs/Verify-Reloader-Working.md

@@ -0,0 +1,51 @@
+# Verify Reloader's Working
+
+Reloader's working can be verified by two ways.
+
+## Verify from logs
+
+Check the logs of reloader and verify that you can see logs looks like below, if you are able to find these logs then it means reloader is working.
+
+```text
+Changes Detected in test-object of type 'SECRET' in namespace: test-reloader
+
+Updated test-resource of type Deployment in namespace: test-reloader
+```
+
+Below are the details that explain these logs:
+
+### test-object
+
+`test-object` is the name of a `secret` or a `deployment` in which change has been detected.
+
+### SECRET
+
+`SECRET` is the type of `test-object`. It can either be `SECRET` or `CONFIGMAP`
+
+### test-reloader
+
+`test-reloader` is the name of namespace in which reloader has detected the change.
+
+### test-resource
+
+`test-resource` is the name of resource which is going to be updated
+
+### Deployment
+
+`Deployment` is the type of `test-resource`. It can either be a `Deployment`, `Daemonset` or `Statefulset`
+
+## Verify by checking the age of Pod
+
+A pod's age can tell whether reloader is working correctly or not. If you know that a change in a `secret` or `configmap` has occurred, then check the relevant Pod's age immediately. It should be newly created few moments ago.
+
+### Verify from kubernetes Dashboard
+
+`kubernetes dashboard` can be used to verify the working of Reloader. After a change in `secret` or `configmap`, check the relevant Pod's age from dashboard. It should be newly created few moments ago.
+
+### Verify from command line
+
+After a change in `secret` or `configmap`. Run the below mentioned command and verify that the pod is newly created.
+
+```bash
+kubectl get pods <pod name> -n <namespace name>
+```