fix: Fallback to default Che tls secret only if CR has empty value for it #576
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
Signed-off-by: Mykola Morhun <[email protected]>
mmorhun
requested review from
davidfestal,
tolusha,
sleshchenko and
AndrienkoAleksandr
mmorhun
changed the title
tolusha
approved these changes
Mar 12, 2020
AndrienkoAleksandr
approved these changes
Mar 13, 2020
45 tasks
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.
Signed-off-by: Mykola Morhun [email protected]
What does this PR do?
Uses default
che-tlssecret name for securing Che only if Che CR has no value specified.What issues does this PR fix or reference?
eclipse-che/che#16280