Upd chart to use sleek 0.1.4

Author: Thierry

helm/prometheus-sleeker/Chart.yaml

@@ -15,10 +15,10 @@ type: application
 # This is the chart version. This version number should be incremented each time you make changes
 # to the chart and its templates, including the app version.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 0.1.12
+version: 0.1.13
 
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to
 # follow Semantic Versioning. They should reflect the version the application is using.
 # It is recommended to use it with quotes.
-appVersion: 0.1.3
+appVersion: 0.1.4

helm/prometheus-sleeker/values.yaml

@@ -8,7 +8,7 @@ image:
   repository: eu.gcr.io/quortex-registry-public/prometheus-sleeker
   pullPolicy: IfNotPresent
   # Overrides the image tag whose default is the chart appVersion.
-  tag: 0.1.3
+  tag: 0.1.4
 
 imagePullSecrets: []
 nameOverride: ""
@@ -25,18 +25,21 @@ serviceAccount:
 
 podAnnotations: {}
 
-podSecurityContext: {}
+podSecurityContext:
+  {}
   # fsGroup: 2000
 
-securityContext: {}
+securityContext:
+  {}
   # capabilities:
   #   drop:
   #   - ALL
   # readOnlyRootFilesystem: true
   # runAsNonRoot: true
   # runAsUser: 1000
 
-resources: {}
+resources:
+  {}
   # We usually recommend not to specify default resources and to leave this as a conscious
   # choice for the user. This also increases chances charts run on environments with little
   # resources, such as Minikube. If you do want to specify resources, uncomment the following
@@ -57,7 +60,7 @@ affinity: {}
 sleekerConfig: {}
 
 # Additional backend container environment variables
-# 
+#
 # A key/value map, where the value is a map, defining either the "value" or
 # "valueFrom" field.
 #