k6-operator icon indicating copy to clipboard operation
k6-operator copied to clipboard

Increase readiness and liveness probe timeouts, introduce an initial delay

Open frittentheke opened this issue 1 year ago • 3 comments
trafficstars

Currently the default timeout of 1 second and no initial delay is applied to the probes of the runner pods. Depending on the startup time this can cause random Pod errors causing a whole TestRun to fail.

At some point it might also make sense to introduce a startupProbe to cover the longer initial startup time a K6 instance (Pod) might need instead of every increasing the runtime liveness and readiness checks.

Fixes #306

frittentheke avatar Aug 12 '24 15:08 frittentheke

CLA assistant check
All committers have signed the CLA.

CLAassistant avatar Aug 13 '24 06:08 CLAassistant

@yorugac Since you opened the issue (https://github.com/grafana/k6-operator/issues/306) PTAL at this proposed fix / mitigation.

As commented, I believe a startup probe would make some sense and also distinguishing between liveness and readiness checks (which have totally different purpose).

frittentheke avatar Aug 13 '24 08:08 frittentheke

any eta when this will go live ? ie increase the timeout of probes

vipul-mykaarma avatar Oct 26 '24 04:10 vipul-mykaarma