Skip to content
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(install): enable/disable crd installation #1693

Merged
merged 1 commit into from
May 12, 2020
Merged

feat(install): enable/disable crd installation #1693

merged 1 commit into from
May 12, 2020

Conversation

kmova
Copy link
Contributor

@kmova kmova commented May 12, 2020

Signed-off-by: kmova kiran.mova@mayadata.io

Why is this PR required? What issue does it fix?:

When helm install for openebs was introduced,
there was no way for helm to install CRDs. So
api-server included the code to install the CRDs
as part of initialization.

With Helm 3, the CRDs can be installed via
helm. There have been some requests for moving
the CRD installations outside of the code for
cases where Kubernetes installers like Lokomotive
and others, would like granular control on
how the required objects are installed.

What this PR does?:

This commit adds an ENV variable that allows
users to enable/disable the CRD install code.

Does this PR require any upgrade changes?:
NA

If the changes in this PR are manually verified, list down the scenarios covered::

Any additional information for your reviewer? :
Mention if this PR is part of any design or a continuation of previous PRs

Checklist:

  • Fixes #
  • PR Title follows the convention of <type>(<scope>): <subject>
  • Has the change log section been updated?
  • Commit has unit tests
  • Commit has integration tests
  • (Optional) Are upgrade changes included in this PR? If not, mention the issue/PR to track:
  • (Optional) If documentation changes are required, which issue on https://github.com/openebs/openebs-docs is used to track them:

When helm install for openebs was introduced,
there was no way for helm to install CRDs. So
api-server included the code to install the CRDs
as part of initialization.

With Helm 3, the CRDs can be installed via
helm. There have been some requests for moving
the CRD installations outside of the code for
cases where Kubernetes installers like Lokomotive
and others, would like granular control on
how the required objects are installed.

This commit adds an ENV variable that allows
users to enable/disable the CRD install code.

Signed-off-by: kmova <kiran.mova@mayadata.io>
Copy link
Contributor

@shubham14bajpai shubham14bajpai left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@akhilerm
Copy link
Contributor

@kmova Is the same set of changes required in NDM, for the installation of BlockDevice and BlockDeviceClaim CRDs?

@kmova
Copy link
Contributor Author

kmova commented May 12, 2020

@akhilerm - probably makes sense to add for NDM as well.

Copy link
Contributor

@prateekpandey14 prateekpandey14 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants