In our company, we are using k8s in version 1.19 or older (have access to helm only). When we do deployment, there is a listener that will create some secrets that we need to mount in our pod. The thing is, such listener is doing his job in pretty late, and the deployment is scaled down to 0 after 10-15 minutes, because CrashLoopBackOff issue.
Is there any way to enforce deployment to keep trying initialize pod? I tried many things like increase livenessProbe
and readinessProbe
with adding failutreTreshold
as 60 and period seconds as 30, so I think it should keep trying to check it for 30 * 60, but it doesn't.
Also I tried to set progressDeadlineSeconds
to something like 3600 (one hour), but it doesn't work as well. No idea what to do.