fix the solution to trigger a deployment on every helm upgrade

Author: tchia04

README.md

@@ -16,7 +16,7 @@ helm install mywebapp-release webapp1/ --values webapp1/values.yaml
 
 # Upgrade after templating
 ```
-helm upgrade mywebapp-release webapp1/ --values mywebapp/values.yaml
+helm upgrade mywebapp-release webapp1/ --values webapp1/values.yaml
 ```
 
 # Accessing it

solution/webapp1/Chart.yaml

@@ -15,7 +15,7 @@ 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.0
+version: 0.1.1
 
 # 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

solution/webapp1/templates/deployment.yaml

@@ -16,6 +16,11 @@ spec:
       labels:
         app: {{ .Values.appName }}
         tier: frontend
+      annotations:
+        # To force pod recreation on every upgrade, 
+        # you can add annotations or checksums to the pod template that change on each upgrade.
+        rollme: {{ randAlphaNum 5 | quote }}    
+    
     spec: # Pod spec
       containers:
       - name: mycontainer

solution/webapp1/values.yaml

@@ -9,7 +9,7 @@ namespace: default
 configmap:
   name: myhelmapp-configmap-v1
   data:
-    CUSTOM_HEADER: 'This app was deployed with helm!'
+    CUSTOM_HEADER: 'Fixed the update issue with helm. This app was deployed with helm!'
 
 image:
   name: devopsjourney1/mywebapp