To fix tls issue in OpenShift #1248
Merged
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
Alevsk
approved these changes
Aug 22, 2022
pjuarezd
approved these changes
Aug 22, 2022
reivaj05
approved these changes
Aug 22, 2022
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.
Fixes: #1234
The idea is to allow Service to use Secret in annotations for tls issue to get solved when installing Operator in OpenShift.
Tested in Openshift version 4.11.0 but user reported issue in 4.10.0 as well.
This change is ignored when not in Openshift cluster.
2022/08/10 14:30:03 http: TLS handshake error from 10.128.0.1:54964: remote error: tls: bad certificateis goneDocumentation: