Figured it out myself.
Realized that the temporaltest-history didn’t start due to limited resource quota to our namespace.
But kubectl get pods didn’t show the temporaltest-hisotry pod, so I easily missed that out.
kubectl describe events came to rescue.
I had to specify resources in the chart to fix the issue.
2 Likes