Include the latest 0.0.14 version in all docs and yaml

Author: peterjenkins1

README.md

@@ -65,10 +65,10 @@ If this is helpful, consider supporting the project :)
 
 ## Requirements
 
-Current version `0.0.11` is tested for Kubernetes >= 1.19 up to 1.27.3
+Current version `0.0.14` is tested for Kubernetes >= 1.19 up to 1.27.3
 For older Kubernetes (<1.19) use the image tag `0.0.6` in your helm values file.
 
-architectures available (0.0.11):
+architectures available (0.0.14):
 
 SHA256 ed12e8f3e630 | linux | 386
 SHA256 91b0285f5398 | linux | amd64

charts/cluster-secret/README.md

@@ -56,7 +56,7 @@ Clustersecrets automates this. It keep track of any modification in your secret
 
 ## Requirements
 
-Current is 0.0.12 tested on > 1.27.1
+Current is 0.0.14 tested on > 1.27.1
 Version 0.0.9 is tested for Kubernetes >= 1.19 up to 1.27.1
 
 For older kubernes (<1.19) use the image tag "0.0.6" in  yaml/02_deployment.yaml

charts/cluster-secret/values.yaml

@@ -1,7 +1,7 @@
 imagePullSecrets: []
 image:
   repository: quay.io/clustersecret/clustersecret
-  tag: 0.0.12
+  tag: 0.0.14
   # use tag-alt for ARM and other alternative builds - read the readme for more information
 
 # If Clustersecret is about to create a secret and then it founds it exists:

yaml/02_deployment.yaml

@@ -19,15 +19,15 @@ spec:
         # - name: regcred
         containers:
         - name: clustersecret
-          image: quay.io/clustersecret/clustersecret:0.0.11
+          image: quay.io/clustersecret/clustersecret:0.0.14
           livenessProbe:
             httpGet:
               path: /healthz
               port: 8080
             periodSeconds: 120
           env:
             - name: CLUSTER_SECRET_VERSION
-              value: "v0.0.11"
+              value: "v0.0.14"
             - name: REPLACE_EXISTING
               value: "false"
           # imagePullPolicy: Always