Skip to content

feat: add OCP version compatibility metadata - #170

Open
p-rog wants to merge 1 commit into
validatedpatterns:mainfrom
p-rog:compatibility-check
Open

feat: add OCP version compatibility metadata#170
p-rog wants to merge 1 commit into
validatedpatterns:mainfrom
p-rog:compatibility-check

Conversation

@p-rog

@p-rog p-rog commented Aug 4, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Adds ocp_versions section to pattern-metadata.yaml declaring OCP 4.20 as the minimum supported version and OCP 4.23 as explicitly unsupported (not yet validated)
  • First pattern to adopt the framework-level OCP version compatibility check

Metadata added

ocp_versions:
  minimum: "4.20"
  unsupported:
    - version: "4.23"
      reason: "Not yet validated — operator catalog and channel availability unconfirmed"

Dependency

Requires the validate_ocp_version role from rhvp.cluster_utils#151 to be merged first. Without it, this metadata is inert (no validation runs).

Context

Supersedes the ZTVP-specific implementation in #163, which was closed in favor of a framework-level solution.

Made with Cursor

Add ocp_versions section to pattern-metadata.yaml declaring OCP 4.20
as the minimum supported version and 4.23 as explicitly unsupported
(not yet validated). Works with the validate_ocp_version role in
rhvp.cluster_utils to check cluster compatibility before installation.

Signed-off-by: Przemyslaw Roguski <proguski@redhat.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant