Bug 1884477: Update bundle manifests to reflect latest CRD state

[periklis]

Description

This PR addresses the sync between our latest CRD state into our bundle manifest directory. This is mandatory to provide an up2date 4.6.0 bundle image.

/cc @blockloop
/assign @ewolinetz

Links

• Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1884477

[openshift-ci-robot]

@periklis: This pull request references Bugzilla bug 1884477, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target release (4.6.0) matches configured target release for branch (4.6.0)
• bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

In response to this:

Bug 1884477: Update bundle manifests to reflect latest CRD state

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/test-infra repository.

[blockloop]

/lgtm

[ewolinetz]

required in line

[ewolinetz]

this isn't required for 4.6.0 since ART is building bundle images from our manifest dir, but it will be required for our post 4.6.z release
/lgtm

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: blockloop, ewolinetz, periklis

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [ewolinetz]

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

[openshift-bot]

/retest

Please review the full test history for this PR and help us cut down flakes.

[ewolinetz]

/hold
@periklis can you target this at master-post-release instead?

[periklis]

/hold
@periklis can you target this at master-post-release instead?

Why? branch cut happened last friday, thus 4.7 == master.

[ewolinetz]

/hold cancel

[openshift-bot]

/retest

Please review the full test history for this PR and help us cut down flakes.

[openshift-ci-robot]

@periklis: Some pull requests linked via external trackers have merged:

The following pull requests linked via external trackers have not merged:

• openshift/cluster-logging-operator#723 is open

These pull request must merge or be unlinked from the Bugzilla bug in order for it to move to the next state.

Bugzilla bug 1884477 has not been moved to the MODIFIED state.

In response to this:

Bug 1884477: Update bundle manifests to reflect latest CRD state

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/test-infra repository.