-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
csi: enable csi-omap based on key in operator config #105
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think deployment generation will change after 107, will re-review after that.
pls rebase, it's a bit confusing to review in current state, thanks. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
after going through the code, just thinking, what's the down side of always deploying this sidecar?
5dced9d
to
e7891c5
Compare
bc255a4
to
3d787c1
Compare
LGTM |
f05f083
to
8a8f141
Compare
5f697a8
to
0702bce
Compare
Signed-off-by: Rewant Soni <[email protected]>
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: nb-ohad, rewantsoni The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
7d92043
into
red-hat-storage:main
The csi-omap generator needs to the enabled on the application cluster for RDR.
Add a new key to operator configMap controller to enable omap. If the key is not set we will always enable this option on operator Config CR. If key is available we will set the value to what was provider in
ocs-client-operator-config