chore: use retries for requests in Keycloak init #4268
Conversation
This file contains hidden or 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
Without retries the job immediately restarts and it takes a long time to get a deployment up and running when the ingress TLS is slowly getting propagated.
Collaborator
|
You can access the deployment of this PR at https://ci-renku-4268.dev.renku.ch |
olevski
force-pushed
the
chore-add-retries-to-keycloak-init-job
branch
2 times, most recently
from
1ed4382 to
e875b31
Compare
aledegano
approved these changes
Nov 28, 2025
Contributor
|
Great idea!!! |
olevski
force-pushed
the
chore-add-retries-to-keycloak-init-job
branch
from
e875b31 to
f3c5740
Compare
Member
Author
|
@aledegano I bumped the wait time for tls and name resolution to 2mins. Then we are down to the jobs restarting with an exponential backoff. Now I reached the limit for certificates from letsencrypt. But it should work. I will rerun on Monday and merge then. |
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.
Without retries the job immediately restarts and it takes a long time to get a deployment up and running when the ingress TLS is slowly getting propagated.
/deploy