This repository has been archived by the owner on Oct 20, 2022. It is now read-only.
Added a possibility to configure readinessProbe timeouts for operator deployment #362
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
PERES-Richard
suggested changes
Sep 14, 2021
There was a problem hiding this comment.
Hi, can you also update the documentation as well please.
@cscetbon What do you think ?
Updated docs |
PERES-Richard
approved these changes
Sep 15, 2021
Merged
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What's in this PR?
Added a possibility to configure readinessProbe timeouts for operator deployment via
values.yamlfile.Why?
We encountered on a problem that after upgrade of operator its deployment object cannot be marked as "ready".
There is a workaround: we have to increase "failureThreshold" timeout to value higher than 1s and everything works correctly
Checklist