Skip to content

Comments

OCPCLOUD-3322: Update to new manifests-gen#150

Open
theobarberbany wants to merge 2 commits intoopenshift:mainfrom
theobarberbany:manifests-gen
Open

OCPCLOUD-3322: Update to new manifests-gen#150
theobarberbany wants to merge 2 commits intoopenshift:mainfrom
theobarberbany:manifests-gen

Conversation

@theobarberbany
Copy link

Summary

  • Vendor latest manifests-gen from cluster-capi-operator
  • Migrate from old CVO ConfigMap manifest delivery to new image-embedded manifests
  • Generated manifests now at openshift/capi-operator-manifests/default/ using the new metadata format (name, attributes, selfImageRef, installOrder)

Test plan

  • make -C openshift ocp-manifests regenerates without drift
  • make -C openshift verify passes
  • Operator installs provider correctly on PowerVS cluster

🤖 Generated with Claude Code

theobarberbany and others added 2 commits February 18, 2026 21:23
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@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 18, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 18, 2026

@theobarberbany: This pull request references OCPCLOUD-3324 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:

Summary

  • Vendor latest manifests-gen from cluster-capi-operator
  • Migrate from old CVO ConfigMap manifest delivery to new image-embedded manifests
  • Generated manifests now at openshift/capi-operator-manifests/default/ using the new metadata format (name, attributes, selfImageRef, installOrder)

Test plan

  • make -C openshift ocp-manifests regenerates without drift
  • make -C openshift verify passes
  • Operator installs provider correctly on PowerVS cluster

🤖 Generated with Claude Code

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.

@theobarberbany theobarberbany changed the title OCPCLOUD-3324: Update to new manifests-gen OCPCLOUD-3322: Update to new manifests-gen Feb 18, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 18, 2026

@theobarberbany: This pull request references OCPCLOUD-3322 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:

Summary

  • Vendor latest manifests-gen from cluster-capi-operator
  • Migrate from old CVO ConfigMap manifest delivery to new image-embedded manifests
  • Generated manifests now at openshift/capi-operator-manifests/default/ using the new metadata format (name, attributes, selfImageRef, installOrder)

Test plan

  • make -C openshift ocp-manifests regenerates without drift
  • make -C openshift verify passes
  • Operator installs provider correctly on PowerVS cluster

🤖 Generated with Claude Code

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.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 18, 2026

@theobarberbany: all tests passed!

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.

@JoelSpeed
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 19, 2026
@theobarberbany
Copy link
Author

theobarberbany commented Feb 19, 2026

We don't have an e2e configured in release. I'm not sure if theres some way we can get signal.

@theobarberbany
Copy link
Author

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 19, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: theobarberbany
Once this PR has been reviewed and has the lgtm label, please ask for approval from joelspeed. 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants