-
Notifications
You must be signed in to change notification settings - Fork 467
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-configurer] Pod should become unhealthy after failing many retries to apply config #1749
Comments
vault-configurer
should become unhealthy after failing many retries to apply config
Thank you for your contribution! This issue has been automatically marked as |
Hiya @Gentoli, thanks for reporting this! We could add an option (flag/env) to control the number of allowed retries before exiting with an error which should resolve this issue. However, as this requires extensions to other components as well (including the CRs), we'd have to plan it ahead. If there's still interest for this feature, we could add it to our backlog. Cheers! |
Is your feature request related to a problem? Please describe.
vault-configurer
pod created by the Vault CR fails to apply vault config. There is no clear indication on it failed either in the pod health check or Vault CR status. Had to check logs to see the failure.Vault CR status:
Describe the solution you'd like
vault-configurer
pod should becomes unhealthy indicating an issue after number of retiresvault-configurer
failedDescribe alternatives you've considered
None
Additional context
I am running in GKE with usually only a single node but with the vault CR configured to schedule two pods on different nodes in case of upgrade or replacing node (one pod is usually stuck on unschedulable).Edit: Scaled the size to 1 and the Vault CR shows healthy even when
vault-configurer
stuck retrying.The text was updated successfully, but these errors were encountered: