-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Timeout on stateful sets #225
Comments
Hi @Teots ! This is something we've run into internally at Shopify as well, and we've been discussing possible solutions. It's true that progressDeadlineSeconds / the "progressing" status condition is not currently available on StatefulSet. What would be the ideal behaviour, in your experience? A would be hairiest to implement/maintain. B or D could be implemented generically for any resource type. C is similar to something we're already working on for deployments, except that SS don't have an existing concept of minimum availability for us to leverage (whereas for deployments, that is already part of the rollingUpdate configuration). |
Hi @KnVerey, thanks for your response. In our current setup option D would suffice completely. Deployment is executed by our CD pipeline and thus a long watch isn't an issue as long as we still could specify a hard timeout. Just to avoid getting stuck forever. |
Timeout customization is now available for all resources as of version 0.15.0. Documentation is at https://github.com/Shopify/kubernetes-deploy#customizing-behaviour-with-annotations. |
Hi,
I tried to deploy a stateful set with a high number of replicas and each of them takes a few minutes to start. Eventually, I ran into this error:
StatefulSet/<my_service_name>: TIMED OUT (limit: 600s)
.Is there any way to override this timeout? I've seen this PR, but the
progressDeadlineSeconds
is only available for theDeployment
type and not forStatefulSet
as far as I know.The text was updated successfully, but these errors were encountered: