-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Vault Agent - Self-DDOS due to failure on rendering 1 template causing all templates to be rerendered #26283
Comments
in my case, it keeps retry to render until my VM is out of memory. |
Hi there! What version of Agent are you using? There's a chance that this bug was fixed by this PR: #25497 Previous to that PR, there was no backoff between the retry when the template server had to be restarted. This adds exponential backoff. It'd be helpful if there were logs to show the time around the retry, as if the template server restarts due to a permissions issue as you claim, that'd be something we'd love to fix. |
I just tested it using Vault v1.16.1 and can confirm this is still an issue. Given the following templates:
Template 2:
If the token used by vault agent has access to
Because the read to |
Hi @F21 , thank you so much for your response. Unfortunately, the way that a new consul-template runner is initialize prevents us from "removing" and "adding" a new template, because there are dependencies that are created between templates that allow it to be accessible from other templates. For that reason, we have to restart the template with all of the configs. |
Describe the bug
We have Vault Agent configured to render multiple templates, with each template retrieving certain secrets from Vault using the
{{- with secret "xxx" }}
function. If one template fails to retrieve a secret (perhaps due to a permissions/policy issues), it triggers a retry. At the end of the retry, the runner restarts, forcing all secrets for all templates to be retrieved again and rerendered. This goes into a loop, which effective DDoses our Vault server.To Reproduce
Steps to reproduce the behavior:
Expected behavior
It would be nice if the runner does not restart and rerender all templates, but only retries the failed templates.
Environment:
vault status
): 1.16.0vault version
): 1.16.0Vault server configuration file(s):
N/a
Additional context
N/a
The text was updated successfully, but these errors were encountered: