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
I'm encountering an issue with the provider-argocd when creating applications in ArgoCD that use the Helmfile plugin. The error message "cannot create ArgoCD application" appears, and the logs indicate that templating was in progress without errors, but it gets aborted consistently after 60 seconds.
Interestingly, if I reduce the complexity of my Helmfile, everything works fine, likely because it completes faster than 60 seconds. This suggests there is a timeout requirement for creating resources within 60 seconds, which I need to extend.
How can we reproduce it?
Create an ArgoCD application using the crossplane provider-argocd with a Helmfile plugin that takes longer than 60 seconds to process.
Observe the error message "cannot create ArgoCD application" and the abortion of the templating process after 60 seconds.
Investigated all ArgoCD timeout settings and increased those I thought might be relevant, but this didn't resolve the issue.
Found a pollInterval flag with a default value of 1 minute. I increased it to 2 minutes and applied it via DeploymentRuntimeConfig, but the process still fails after 60 seconds.
Upon reviewing the code, I didn't find any instance of managed.WithPollInterval(o.PollInterval), which leads me to suspect that the pollInterval argument might not be set at all for the provider. In the AWS provider, the poll interval is set explicitly, as shown here: AWS provider poll interval example.
Thank you in advance for your help!
The text was updated successfully, but these errors were encountered:
What happened?
I'm encountering an issue with the
provider-argocd
when creating applications in ArgoCD that use the Helmfile plugin. The error message"cannot create ArgoCD application"
appears, and the logs indicate that templating was in progress without errors, but it gets aborted consistently after 60 seconds.Interestingly, if I reduce the complexity of my Helmfile, everything works fine, likely because it completes faster than 60 seconds. This suggests there is a timeout requirement for creating resources within 60 seconds, which I need to extend.
How can we reproduce it?
crossplane provider-argocd
with a Helmfile plugin that takes longer than 60 seconds to process.What environment did it happen in?
xpkg.upbound.io/crossplane-contrib/provider-argocd:v0.7.0
Additional Details
Here's what I've tried so far:
pollInterval
flag with a default value of 1 minute. I increased it to 2 minutes and applied it viaDeploymentRuntimeConfig
, but the process still fails after 60 seconds.Upon reviewing the code, I didn't find any instance of
managed.WithPollInterval(o.PollInterval)
, which leads me to suspect that thepollInterval
argument might not be set at all for the provider. In the AWS provider, the poll interval is set explicitly, as shown here: AWS provider poll interval example.Thank you in advance for your help!
The text was updated successfully, but these errors were encountered: