add startupProbe for web

[chris93111]

SUMMARY

Wen controlplane scale the container is go to ready fastly and the web/api is not ready, so client has 503 response

The startupProbe allows to protect time for starting web/api in autoscale scenario

ISSUE TYPE

503 in autoscale scenario

ADDITIONAL INFORMATION

Maybe the value of failureThreshold is incorrect, the django migration can put more time in update or initial scenario

[chris93111]

any update ?

[fosterseth]

@chris93111 do you mind rebasing and resolving the conflicts? the deployment is now split into web and task

[chris93111]

@chris93111 do you mind rebasing and resolving the conflicts? the deployment is now split into web and task

Ok

[chris93111]

Hi @fosterseth

sorry for the time

rebase and conflicts resolved

readiness add to web deployment

[rooftopcellist]

@chris93111 Is there a specific reason why we would want a startupProbe here rather than intialDelaySeconds on a readinessProbe?

FYI, there is a PR here for adding the readiness and liveliness probes that is actively being reviewed as well:

• Add -ness checks and refactor migrations #1674

[rooftopcellist]

This feature has been merged as part of #1674. It is not technically a startupProbe, but serves the same purpose as a readinessProbe. If this does not resolve your issue, please open a new issue.