[release-4.15] create a mechanism to deploy odf using operator-sdk

[iamniting]

This is an manual cherry-pick of #394 #412

[openshift-ci]

@iamniting: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

[release-4.15] create a mechanism to deploy odf using operator-sdk

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-sigs/prow repository.

[iamniting]

/test images

[malayparida2000]

/lgtm

[malayparida2000]

/lgtm cancel

[Nikhil-Ladha]

/lgtm

[Nikhil-Ladha]

/lgtm

[openshift-ci]

@iamniting: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

[release-4.15] create a mechanism to deploy odf using operator-sdk

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-sigs/prow repository.

[iamniting]

/retest-required

[iamniting]

/retest images

[openshift-ci]

@iamniting: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:

• /test ci-bundle-odf-operator-bundle
• /test images
• /test odf-operator-e2e-aws

Use /test all to run all jobs.

In response to this:

/retest images

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-sigs/prow repository.

[iamniting]

/test images

[iamniting]

/test odf-operator-e2e-aws

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

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

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:

• OWNERS [iamniting]

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

[iamniting]

/cherry-pick release-4.14
/cherry-pick release-4.13
/cherry-pick release-4.12

[openshift-cherrypick-robot]

@iamniting: new pull request created: #447

In response to this:

/cherry-pick release-4.14
/cherry-pick release-4.13
/cherry-pick release-4.12

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-sigs/prow repository.

[iamniting]

/cherry-pick release-4.13

[openshift-cherrypick-robot]

@iamniting: #440 failed to apply on top of branch "release-4.13":

Applying: makefile: create a separate catalog image for deps
Using index info to reconstruct a base tree...
M	Makefile
M	hack/make-bundle-vars.mk
Falling back to patching base and 3-way merge...
Auto-merging hack/make-bundle-vars.mk
Auto-merging Makefile
Applying: action: update action to verify catalog changes
Using index info to reconstruct a base tree...
M	.github/workflows/docker-build.yaml
Falling back to patching base and 3-way merge...
Auto-merging .github/workflows/docker-build.yaml
CONFLICT (content): Merge conflict in .github/workflows/docker-build.yaml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0002 action: update action to verify catalog changes
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-4.13

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-sigs/prow repository.