Make the initJob's backoff limit configurable via values.yaml #147
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
No problem! Thank you to the rest of the zitadel team for always being so responsive and helpful! |
kleberbaum
pushed a commit
to fhkit/zitadel-charts
that referenced
this pull request
May 24, 2024
…l#147) * Update values.yaml - make the backoff limit configurable * Update Chart.yaml - bump chart a patch version after making initJob.backoffLimit configurable * Update initjob.yaml - make spec.backoffLimit value configurable in values.yaml
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Definition of Ready
This makes the initJob's backoffLimit configurable, so that it will restart as much as needed while waiting for mounted database TLS secrets to become available. This helps when databases are slower to provision than zitadel expects if you're deploying both at the same time.