Use Openshift Cluster API instead of MachineAPIOperator#5331
Use Openshift Cluster API instead of MachineAPIOperator#5331openshift-merge-robot merged 2 commits intoopenshift:masterfrom kirankt:openshift-api-instead-of-mao
Conversation
openshift-ci
bot
added
the
do-not-merge/work-in-progress
staebler
left a comment
staebler
left a comment
There was a problem hiding this comment.
/lgtm
/hold for some optional tests to pass
openshift-ci
bot
added
the
do-not-merge/hold
|
/test e2e-aws |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: staebler The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
bot
added
the
approved
|
/retest |
kirankt
changed the title
openshift-ci
bot
removed
the
do-not-merge/work-in-progress
|
/retest All of the failing tests have successful installs, so I doubt any of the failures are related to this PR. |
|
/retest |
|
/test e2e-aws I think this is the only test we should be waiting on. It looks like rhel workers is permafailing again and e2e-crc is not a reliable test. |
|
/hold cancel |
openshift-ci
bot
removed
the
do-not-merge/hold
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
2 similar comments
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/hold |
openshift-ci
bot
added
the
do-not-merge/hold
|
/hold cancel This looks good, but I suspect we might be able to do much more in this area. I will follow up on it and report back here or in slack. |
openshift-ci
bot
removed
the
do-not-merge/hold
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
8 similar comments
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
@kirankt: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. I understand the commands that are listed here. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
7 similar comments
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
5 participants
Reduce the references to MachineAPIOperator for Cluster API and instead we will utilize OpenShift API. The MachineAPIOperator must still be vendored for the time being because of the vsphere CAPI provider resides within its repo unlike other providers who have their own separate repo.