[ART-11115] Remove ose-alibaba-machine-controllers

[vfreex]

No description provided.

[vfreex]

/cherry-pick openshift-4.17

[openshift-cherrypick-robot]

@vfreex: once the present PR merges, I will cherry-pick it on top of openshift-4.17 in a new PR and assign it to you.

In response to this:

/cherry-pick openshift-4.17

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.

[joepvd]

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: joepvd

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 [joepvd]

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

[openshift-cherrypick-robot]

@vfreex: #5602 failed to apply on top of branch "openshift-4.17":

Applying: Remove ose-alibaba-machine-controllers
Using index info to reconstruct a base tree...
M	images/ose-alibaba-machine-controllers.yml
Falling back to patching base and 3-way merge...
CONFLICT (modify/delete): images/ose-alibaba-machine-controllers.yml deleted in Remove ose-alibaba-machine-controllers and modified in HEAD. Version HEAD of images/ose-alibaba-machine-controllers.yml left in tree.
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 Remove ose-alibaba-machine-controllers

In response to this:

/cherry-pick openshift-4.17

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.