-
Notifications
You must be signed in to change notification settings - Fork 200
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
refact(cvc): move cvc operator to its own deployment #1559
refact(cvc): move cvc operator to its own deployment #1559
Conversation
6513dfc
to
7ee6dfa
Compare
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.
changes are good
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.
LGTM
Signed-off-by: prateekpandey14 <[email protected]>
7ee6dfa
to
6bc7c5e
Compare
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.
Need to refactor to make it easier to keep it modular. Push the targets into specific folder.
Signed-off-by: prateekpandey14 <[email protected]>
75d0f4e
to
e3bcb0e
Compare
Signed-off-by: prateekpandey14 [email protected]
What this PR does / why we need it:
Changes remove the cstorvolumeclaim controller go-routines from the maya-apiserver and will be deployed as its own pod in k8s cluster.
This changes required to be done as cvc controller is specific to CStor CSI volume provisioning and there is no depdencies in Maya-apiserver.
As part of moving further with buiding new controllers/operators specific to each components and there specific repos it will easier to maintain.
Special notes for your reviewer:
This requires a new deployment file to be added as part of cstor-operator, PR openebs/openebs#2868