Open henrywangx opened 1 year ago
Potentially a duplicate of #7179. You can also workaround this by using kubectl
directly in a script
template, for example.
Since #7860 is open, I don't think more will be added to the resource
spec, preferring a plugin instead, but patches that do not change the spec could be acceptable.
activeDeadlineSeconds
as a workaroundPotentially a duplicate of #7179. You can also workaround this by using
kubectl
directly in ascript
template, for example.Since #7860 is open, I don't think more will be added to the
resource
spec, preferring a plugin instead, but patches that do not change the spec could be acceptable.
No, we use the resource
, which uses argo controller's runKubectl
to create/get k8s object. And we faced the hang problem when it try to get object's status.
I think you misunderstood me. I mentioned a script
for workaround purposes.
Otherwise #7179 and #7860 are indeed about resource
templates.
Have you tried the workaround I mentioned in https://github.com/argoproj/argo-workflows/issues/5549#issuecomment-810448427?
Summary
add "Timeout" option and retry for function
runKubectl
.Use Cases
runKubectl
will hang. We need to set a reasonable timeout and retry after few seconds.Message from the maintainers:
Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.