Timeout from Postgresql statestore following runtime upgrade from 1.16 to 1.17 | Dapr | Page 1

We've upgraded one of our environments from 1.16 to 1.17 (running in k8s)
Following this upgrade dapr-sidecars got into a crash loop.
After setting a much longer livenessProbes than the provided defaults we believe the root cause is with some migration of the Postgresql State-Stores.

We've prolonged the initTimeout to a few minutes and are now consistently getting the bellow logs

Any recommendation what to do in this case or what will be a reasonable initTimeout?

#Timeout from Postgresql statestore following runtime upgrade from 1.16 to 1.17