"helm upgrade" doesn't trigger a redeployment

[tchia04]

I watched the video at https://www.youtube.com/watch?v=jUYNS90nq8U&t=147s

At around 9:20 into the video, the helm file was updated and "helm upgrade" was ran and kubectl get all shows old pods terminating and the new pod is created.

I tried the same thing and it didn't delete the pod and create new pod

I had to run "helm uninstall" and then "helm install" to see the change I made to the configMap.

here are my version numbers

❯ helm version
version.BuildInfo{Version:"v3.15.2", GitCommit:"1a500d5625419a524fdae4b33de351cc4f58ec35", GitTreeState:"clean", GoVersion:"go1.22.4"}

❯ minikube version
minikube version: v1.33.1
commit: 5883c09216182566a63dff4c326a6fc9ed2982ff

❯ kubectl version
Client Version: v1.30.2
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.30.0

When I did deeper, I found there is a new way to force recreate of the pods.
See https://github.com/helm/helm-www/pull/286/files

[jaiswal09]

kubectl config use-context docker-desktop