CORS-3830: Add missing supported platforms in top-level README

[tthvo]

Supported platform list:

• Remove ovirt, libvirt and its documentations (no longer supported).
• Added ibmcloud, nutanix and powervs

[openshift-ci-robot]

@tthvo: This pull request references CORS-3830 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

Details

In response to this:

Supported platform list:

• Remove ovirt and its documentations (no longer supported).
• Added ibmcloud, nutanix and powervs

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 openshift-eng/jira-lifecycle-plugin repository.

[tthvo]

/cc @patrickdillon

[patrickdillon]

Also can you remove Libvirt? We don't support that any longer either

[tthvo]

Also can you remove Libvirt? We don't support that any longer either

Yup, make sense! That is now removed in the latest commits.

[openshift-ci-robot]

@tthvo: This pull request references CORS-3830 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

Details

In response to this:

Supported platform list:

• Remove ovirt, libvirt and its documentations (no longer supported).
• Added ibmcloud, nutanix and powervs

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 openshift-eng/jira-lifecycle-plugin repository.

[tthvo]

/jira refresh

[openshift-ci-robot]

@tthvo: This pull request references CORS-3830 which is a valid jira issue.

Details

In response to this:

/jira refresh

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 openshift-eng/jira-lifecycle-plugin repository.

[patrickdillon]

Sorry for potential bikeshedding here, but now that we're in here making changes, I feel like it's a good time to really clean it up--then we can come back in many years :D

So walking back a couple of my earlier suggestions:

1. It seems like Power VS is the more commonly accepted form
2. The duplication of platforms seems like it could be improved. How about something like this:

• AWS (Official Docs)
• Bare Metal (Official Docs)
• GCP (Official Docs)
  and so on...

That is, the anchor text for each platform would take it to the in-repo docs directory (if it exists) and then we have a separate link to official docs (using latest for version in the url).

I know that's a little vague but hopefully makes sense.

[tthvo]

That is, the anchor text for each platform would take it to the in-repo docs directory (if it exists) and then we have a separate link to official docs (using latest for version in the url).

That makes sense to me! It looks very much cleaner and has links to official docs now :D

[patrickdillon]

/approve
/lgtm

Typically we might want to be more careful with squashing commits, but in this case I think it makes sense to just squash them all, so we can use tide to do that

/label tide/merge-method-squash

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: patrickdillon

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [patrickdillon]

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

[openshift-ci]

@tthvo: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-vsphere-externallb-ovn	9dc14d1	link	false	/test e2e-vsphere-externallb-ovn
ci/prow/e2e-vsphere-ovn-multi-network	9dc14d1	link	false	/test e2e-vsphere-ovn-multi-network
ci/prow/e2e-vsphere-host-groups-ovn-custom-no-upgrade	9dc14d1	link	false	/test e2e-vsphere-host-groups-ovn-custom-no-upgrade
ci/prow/e2e-azure-ovn-resourcegroup	9dc14d1	link	false	/test e2e-azure-ovn-resourcegroup

Full PR test history. Your PR dashboard.

Details

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. I understand the commands that are listed here.

[patrickdillon]

/label acknowledge-critical-fixes-only

[openshift-bot]

[ART PR BUILD NOTIFIER]

Distgit: ose-installer-terraform-providers
This PR has been included in build ose-installer-terraform-providers-container-v4.19.0-202501292227.p0.g1e5a97e.assembly.stream.el9.
All builds following this will include this PR.

[openshift-bot]

[ART PR BUILD NOTIFIER]

Distgit: ose-installer-altinfra
This PR has been included in build ose-installer-altinfra-container-v4.19.0-202501292227.p0.g1e5a97e.assembly.stream.el9.
All builds following this will include this PR.

[openshift-bot]

[ART PR BUILD NOTIFIER]

Distgit: ose-baremetal-installer
This PR has been included in build ose-baremetal-installer-container-v4.19.0-202501292227.p0.g1e5a97e.assembly.stream.el9.
All builds following this will include this PR.

[openshift-bot]

[ART PR BUILD NOTIFIER]

Distgit: ose-installer-artifacts
This PR has been included in build ose-installer-artifacts-container-v4.19.0-202501292227.p0.g1e5a97e.assembly.stream.el9.
All builds following this will include this PR.