[Documentation] Add Support/Validated Matrix for Components.

[joshuayao]

Priority

Undecided

OS type

Ubuntu

Hardware type

Xeon-GNR

Running nodes

Single Node

Description

The matrix should include the supported/validated models, serving F/W, hardware etc.

[kmishra1204]

I strongly support this direction and suggest a minimal matrix schema to keep it maintainable:

Suggested columns

• Component name
• Status (experimental / beta / validated)
• Last validated date
• Supported model/provider set
• Deployment targets tested (k8s, compose, etc.)
• Security notes link
• Maintainer/contact

Suggested process

1. Keep matrix in a single source file (YAML/JSON) in repo.
2. Generate docs table from source to avoid drift.
3. Add CI check that fails when docs table and source diverge.
4. Require matrix update in PR checklist for component-affecting changes.

This would make OPEA much easier to evaluate for production readiness in enterprise environments.

[kmishra1204]

Following up with a concrete next step that keeps this lightweight:

• Add a matrix source file (for example docs/compatibility-matrix.yaml).
• • Generate the docs table from that source in CI to prevent drift.
• • • Validate required fields (component, status, last_validated, hardware, provider).
• • • • Add a PR checklist item: "matrix updated or N/A".
        If this direction works, I can open a small doc + schema starter PR for maintainers to iterate on.