You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to this in docs: https://skaffold.dev/docs/status-check/#configuring-timeout-for-status-check
in case that both statusCheckDeadlineSeconds and Deployment.spec.progressDeadlineSeconds are set in skaffold.yaml, precedence is given to Deployment.spec.progressDeadline only if it is less than statusCheckDeadlineSeconds.
Actual behavior
When the following is set in deploy section of skaffold.yaml: statusCheckDeadlineSeconds: 5 and the k8s deployment contains: progressDeadlineSeconds: 60 (more than the status-check timeout) then deployments that lasts more than 5s are not interrupted by skaffold
DEBU[0011] Running command: [kubectl --context microk8s rollout status deployment nodejs-app-deployment --namespace default --watch=false] subtask=0 task=Deploy
DEBU[0011] Command output: [deployment "nodejs-app-deployment" successfully rolled out
] subtask=0 task=Deploy
- deployment/nodejs-app-deployment is ready.
Deployments stabilized in 11.051 seconds
INFO[0011] Deploy completed in 11.614 seconds subtask=-1 task=Deploy
DEBU[0011] getting client config for kubeContext: `microk8s` subtask=-1 task=DevLoop
Having above settings once you comment progressDeadlineSeconds: 60 in k8s deployment status-check interrupts after 5s
DEBU[0006] Running command: [kubectl --context microk8s rollout status deployment nodejs-app-deployment --namespace default --watch=false] subtask=0 task=Deploy
DEBU[0006] pod statuses could not be fetched this time due to following errors occurred client rate limiter Wait returned an error: context deadline exceeded subtask=0 task=Deploy
DEBU[0006] marking resource failed due to error code STATUSCHECK_USER_CANCELLED subtask=0 task=Deploy
DEBU[0006] setting skaffold deploy status to STATUSCHECK_USER_CANCELLED. subtask=0 task=Deploy
DEBU[0006] Running command: [tput colors] subtask=-1 task=DevLoop
DEBU[0006] Command output: [256
] subtask=-1 task=DevLoop
1/1 deployment(s) failed
Ergo the precedence is given to Deployment.spec.progressDeadline even if it is greater than statusCheckDeadlineSeconds.
Expected behavior
According to this in docs: https://skaffold.dev/docs/status-check/#configuring-timeout-for-status-check
in case that both
statusCheckDeadlineSeconds
andDeployment.spec.progressDeadlineSeconds
are set inskaffold.yaml
, precedence is given toDeployment.spec.progressDeadline
only if it is less thanstatusCheckDeadlineSeconds
.Actual behavior
When the following is set in
deploy
section ofskaffold.yaml
:statusCheckDeadlineSeconds: 5
and the k8s deployment contains:progressDeadlineSeconds: 60
(more than the status-check timeout) then deployments that lasts more than5s
are not interrupted by skaffoldHaving above settings once you comment
progressDeadlineSeconds: 60
in k8s deployment status-check interrupts after5s
Ergo the precedence is given to
Deployment.spec.progressDeadline
even if it is greater thanstatusCheckDeadlineSeconds
.Information
The text was updated successfully, but these errors were encountered: