[OCPBUGS#35239]: Update the compatibility matrix

[tmalove]

Jira: OCPBUGS-35239

Version(s):
This PR is based on the ‘opp-docs-main’ repo and when merged, it should be in that branch only. The OPP doc is not versioned. Add this PR to the ‘Continuous Release’ milestone.

Link to docs preview:
Architecture Updated 6/26/2024)

QE review:

• [x ] QE has approved this change. (Oded R.)

Additional information:
The product versions that are listed might not be the latest available version for the product. The versions listed in the compatibility matrix are the latest verified versions for OPP.

[ocpdocs-previewbot]

🤖 Mon Jul 29 19:00:18 - Prow CI generated the docs preview:

https://77314--ocpdocs-pr.netlify.app/openshift-opp/latest/architecture/opp-architecture.html

[tmalove]

/retest

[tmalove]

@gparvin Will you take a look at the compatibility matrix ? I added the support product versions back to 4.12, but not sure if these versions were actually verified based on the OCP version. I will send Oded a DM since I could not find his @ in GH. Thanks!

Also, the architectural update diagram updates are coming soon.

[gparvin]

We will have an ACM 2.11 release that will be available not long after OCP 4.16 is available. That is the one that should be listed here.

[gparvin]

We should have had ACM 2.8 here. Can you double check to see when we documented ACM 2.8?

[tmalove]

@gparvin after looking at the previous PRs to update the versions, 2.8 follows the trend, however, I will have Oded verify this. Thank you!

[tmalove]

/retest

[tmalove]

@gparvin I modified the original scope of this PR from Updating the architecture overview document and modifying the compatibility matrix to just the matrix updates. I will open a PR for updating the diagram when those changes are underway.
In the meantime, will you ack the matrix changes? You and Oded agreed that ACM 2.8 was verified with OCP 4.13. Thanks!

[gparvin]

This looks right to me.

[tmalove]

/label do-not-merge/hold

[openshift-ci]

@tmalove: The label(s) /label do-not-merge/hold cannot be applied. These labels are supported: acknowledge-critical-fixes-only, platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, no-qe, downstream-change-needed, rebase/manual, cluster-config-api-changed, approved, backport-risk-assessed, bugzilla/valid-bug, cherry-pick-approved, cloud-experts, cnv, dev-tools, distributed-tracing, ims, jira/valid-bug, merge-review-in-progress, merge-review-needed, mtc, multi-arch, oadp, peer-review-done, peer-review-in-progress, peer-review-needed, rhacs, rhv, sd-docs, serverless, service-mesh, sme-review-done, sme-review-needed, staff-eng-approved, telco. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

In response to this:

/label do-not-merge/hold

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.

[tmalove]

/retest

[tmalove]

/label peer-review-needed

[openshift-ci]

@tmalove: all tests passed!

Full PR test history. Your PR dashboard.

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.

[GroceryBoyJr]

/label peer-review-in-progress
/remove-label peer-review-needed
/assign GroceryBoyJr

[GroceryBoyJr]

LGTM

[GroceryBoyJr]

/label peer-review-done
/remove-label peer-review-in-progress
/unassign GroceryBoyJr

[tmalove]

/label merge-review-needed

[opayne1]

/lgtm