Add forced restart of Oathkeeper #1484
Closed
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
… reached after 5 minutes
triffer
changed the title
kyma-bot
added
the
size/L
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.
We often see flaky tests, because Oathkeeper doesn't reach it's minimum availability. Unfortunately, I wasn't possible to reproduce this behaviour to gain more insights why Oathkeeper does not become available.
We also experienced unavailable Oathkeeper deployments on production clusters in the past. We also don't have any insights from those cases. In those cases a restart of the deployment was done and Oathkeeper started successfully.
Because of this knowledge, we can assume that a restart may help Oathkeeper to recover successfully.
Description
Changes proposed in this pull request:
Pre-Merge Checklist
Related issues