updating chart version to 3.3.8 and app version to nightly

deployment/helm/ditto/Chart.yaml

@@ -16,8 +16,8 @@ description: |
   A digital twin is a virtual, cloud based, representation of his real world counterpart
   (real world “Things”, e.g. devices like sensors, smart heating, connected cars, smart grids, EV charging stations etc).
 type: application
-version: 3.3.7  # chart version is effectively set by release-job
-appVersion: 3.3.7
+version: 3.3.8  # chart version is effectively set by release-job
+appVersion: nightly
 keywords:
   - iot-chart
   - digital-twin

deployment/helm/ditto/values.yaml

@@ -206,8 +206,8 @@ ingress:
     #  of its containers crashing, for it to be considered available
     #  ref: https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#min-ready-seconds
     minReadySeconds: 10
-    # as NGINX Ingress Controller on its pod shutdown tends to interrupt connections, we need to include 
-    # some wait time so that existing connections are fully handled before the pod is really shut down. 
+    # as NGINX Ingress Controller on its pod shutdown tends to interrupt connections, we need to include
+    # some wait time so that existing connections are fully handled before the pod is really shut down.
     # ref: https://medium.com/codecademy-engineering/kubernetes-nginx-and-zero-downtime-in-production-2c910c6a5ed8
     preStopWait: 15
     # specify how many old ReplicaSets for ingress controller deployment will be retained