Added new rook bundle creation script

[Nikhil-Ladha]

• Added Dockerfile to create rook-ceph-operator-bundle under the rook repo.
• Updated the Makefile to have the 'bundle' command, that reference the 'gen-bundle.sh' script under build/bundle.
• Moved the rook csv under build/csv/ceph directory to keep all the manifests at one location for bundle creation

Checklist:

• Commit Message Formatting: Commit titles and messages follow guidelines in the developer guide.
• Reviewed the developer guide on Submitting a Pull Request
• Pending release notes updated with breaking and/or notable changes for the next minor release.
• Documentation has been updated, if necessary.
• Unit tests have been added, if necessary.
• Integration tests have been added, if necessary.

[Nikhil-Ladha]

cc @subhamkrai @iamniting

[BlaineEXE]

IIRC, this master branch is just a resync of the master branch from github.com/rook/rook. I think these changes will be un-done the next time the branches are synced. Am I missing something? Or is there a way to make these changes to the Rook upstream as well?

[travisn]

IIRC, this master branch is just a resync of the master branch from github.com/rook/rook. I think these changes will be un-done the next time the branches are synced. Am I missing something? Or is there a way to make these changes to the Rook upstream as well?

The resync should just be bringing the commits from upstream to the downstream. It's not resetting the branch, so the only risk of making changes in the downstream master should be if there are merge conflicts. Also it's important to note that the downstream release branches will be created directly from the upstream branches, so any commits in the downstream master would not be included in the downstream release branches IIUC.

[Nikhil-Ladha]

The resync should just be bringing the commits from upstream to the downstream. It's not resetting the branch, so the only risk of making changes in the downstream master should be if there are merge conflicts. Also it's important to note that the downstream release branches will be created directly from the upstream branches, so any commits in the downstream master would not be included in the downstream release branches IIUC.

The release branches created now are being synced from the downstream master only, though I guess once we have an upstream release that would be reset to an upstream release branch. So, once we get these changes into the master branch d/s, these changes would be synced to the release branch as well.

[Nikhil-Ladha]

Tested the changes and everything is working fine

[openshift-ci]

@iamniting: changing LGTM is restricted to collaborators

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[sp98]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: iamniting, Nikhil-Ladha, sp98, subhamkrai

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment