We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This is mentioned in #78 but it looks like the fix he is working on will only force a retry if the secret does not exist yet.
Would be nice if it also watched for secret changes so it triggered a reload when a certificate gets updated.
The text was updated successfully, but these errors were encountered:
Fixed in #166
Sorry, something went wrong.
No branches or pull requests
This is mentioned in #78 but it looks like the fix he is working on will only force a retry if the secret does not exist yet.
Would be nice if it also watched for secret changes so it triggered a reload when a certificate gets updated.
The text was updated successfully, but these errors were encountered: