Retry Functionality

[saitbai]

Description

Hi, sometimes helm deployments are failing, retry functionality would be appreciated.

Potential Terraform Configuration

resource "helm_release" "example" { .... number_of_retry = 5, }

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key.

References

https://github.com/hashicorp/terraform-provider-http/issues/49

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

[BBBmau]

Hello! Thank you for opening this issue @saitbai, what type of deployment failures are you running into that requires a retry functionality?

[saitbai]

@BBBmau TCP connection issues during deployment to remote cluster.

[dkeightley]

This is perhaps more of a terraform limitation, but just as another example:

A chart containing an Ingress object depends on the availability of the ingress-nginx validating webhook. During cluster provisioning the webhook may take a few more seconds to be available before helm will be able to apply the object.

[Nefilime]

Same issue when deploy cluster and other helms in a same time. There is a time when cluster unavailable and dependency not helped.

[mluscon]

Hi, I would also highly appreciate a retry option because of a webhook unavailability.

[pkit]

Webhooks are unavailable left and right. I need to re-apply the plan 2-3 times to succeed. I understand that most terraform providers give zero priority to clean bootstrap and destroy, but please, consider it.