Skip to content

OCPCLOUD-3184: Implement object schema pruning for compatibility requirements#464

Draft
JoelSpeed wants to merge 17 commits intoopenshift:mainfrom
openshift-cloud-team:compatibility-object-pruning
Draft

OCPCLOUD-3184: Implement object schema pruning for compatibility requirements#464
JoelSpeed wants to merge 17 commits intoopenshift:mainfrom
openshift-cloud-team:compatibility-object-pruning

Conversation

@JoelSpeed
Copy link
Contributor

This implements object schema pruning through a mutating webhook configuration for any resource that has a protective CompatiblityRequirement configured

Currently based on #461, which means only the final 4 commits are pertinent to this PR

@openshift-ci-robot
Copy link

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 16, 2026
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 16, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 16, 2026

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 16, 2026

@JoelSpeed: This pull request references OCPCLOUD-3184 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.22.0" version, but no target version was set.

Details

In response to this:

This implements object schema pruning through a mutating webhook configuration for any resource that has a protective CompatiblityRequirement configured

Currently based on #461, which means only the final 4 commits are pertinent to this PR

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.

@coderabbitai
Copy link

coderabbitai bot commented Feb 16, 2026

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: d29f37b0-e6f7-4151-b849-99a49bbaff12

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 16, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign chrischdi for approval. For more information see the Code Review Process.

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

Details Needs approval from an approver in each of these files:

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

@JoelSpeed JoelSpeed force-pushed the compatibility-object-pruning branch from 57ff46d to 85c8bf4 Compare February 16, 2026 17:00
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 19, 2026
@JoelSpeed JoelSpeed force-pushed the compatibility-object-pruning branch from 85c8bf4 to abdcc99 Compare February 23, 2026 13:59
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 23, 2026
@JoelSpeed JoelSpeed force-pushed the compatibility-object-pruning branch 2 times, most recently from 00d0291 to 161f683 Compare March 3, 2026 15:37
@JoelSpeed JoelSpeed force-pushed the compatibility-object-pruning branch from 161f683 to ba9222a Compare March 4, 2026 13:58
@JoelSpeed JoelSpeed force-pushed the compatibility-object-pruning branch from ba9222a to 8acd414 Compare March 6, 2026 12:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants