-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Backport of Add Nomad RetryConfig to agent template config into release/1.3.x #13997
Backport of Add Nomad RetryConfig to agent template config into release/1.3.x #13997
Conversation
ee5e772
to
62ef297
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is G2G. Waiting for @lgfa29 to concur.
I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions. |
Backport
This PR is auto-generated from #13907 to be assessed for backporting due to the inclusion of the label backport/1.3.x.
WARNING automatic cherry-pick of commits failed. Commits will require human attention.
The below text is copied from the body of the original PR.
Closes #13019
This PR introduces a retry configuration option for Nomad dependencies in Consul Template. For example, Nomad native service discovery and secure variables will make calls to the Nomad API. If connectivity is lost between the client and the servers, these calls will fail and the task may fail or run with stale data forever depending on the type of error. Operators can now specify a
nomad_retry
stanza in the same way they can for Vault or Consul. The default configattempts
is set to0
which allows for infinite retries.