-
Notifications
You must be signed in to change notification settings - Fork 105
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
feat(crd): refactoring CRD #70
Conversation
Codecov Report
@@ Coverage Diff @@
## master #70 +/- ##
=======================================
Coverage 23.57% 23.57%
=======================================
Files 14 14
Lines 475 475
=======================================
Hits 112 112
Misses 362 362
Partials 1 1 Continue to review full report at Codecov.
|
@pawanpraka1 - Can you confirm that the changes are mainly the following: There is no change to the short names, from earlier versions to this version. While I see the reasoning behind cutting the prefix (which seems redundant), I am wondering if we should continue to have them for clarity. When using kubectl, only full name, and the short names matter. This PR takes care of short-names being unique. I think we should maintain the same for full name. Can we revert the changes done to CRD names and only keep the group change. |
Yes @kmova, this PR does two things :-
@kmova, the full name format will change anyway as we are changing the group name since full name format depends on group name So we are changing CRD from zfsvolumes.openebs.io to volumes.zfs.openebs.io. |
1e8e712
to
7538541
Compare
@pawanpraka1 According to the PR message :
I could not find this change or I could be interpreting it wrong. Can you please help here? |
Changed the group name from openebs.io to zfs.openebs.io. Signed-off-by: Pawan <pawan@mayadata.io>
Signed-off-by: Pawan <pawan@mayadata.io>
fixes openebs/openebs#2960
Changed the group name from openebs.io to zfs.openebs.io.
Now ZFS Volume CR will look like this :
Snapshot CR will look like this :