Rollout restart with Vault injector in Kubernetes at 2/3 of max_ttl

This video is exactly what we do. But the tutorial stops just before an important part!
How to manage the application when the database credentials are rotated?

Because just use the kill -HUP signal for example will kill the app, and then the restart counter will be incremented… So not cool!

So we need a solution when the credentials are going to expire.
Find a way to restart the pod/deployment before the max_tll is reached (as we run on Kubernetes)

Hope someone can help!