TLS - add OpenShift compatibility #885
Merged
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
ReSearchITEng
requested review from
CyberDem0n,
FxKu,
Jan-M,
RafiaSabih,
avaczi,
erthalion and
sdudoladov
as code owners
FxKu
reviewed
Mar 30, 2020
|
I'm fine with this change and agree that it's better to remove the hardcoded spiloFsGroup and let users configure it. It's documented and should be fine this way |
FxKu
reviewed
Mar 31, 2020
|
👍 |
|
👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Adds OpenShift compatibility by removing forced injection of fsGroup.
In it's current format, there is no workaround to use TLS in non-priviledged, non-root OpenShift, where fsGroup must not be set , as it's dynamically allocated at creation time.
Solves: #798 (comment)
@zimbatm and @FxKu - please review.