Bug 1969320: [release-4.7] packageserver CSV: add missing properties

[vrutkovs]

Some properties are unset and being set to defaults. CVO is however unware of it, so it attempts to remove the fields which are unset in the manifest files.

This PR should prevent CVO from hotlooping on this manifest.

Cherry-pick of #84 on release-4.7

[openshift-ci]

@vrutkovs: This pull request references Bugzilla bug 1969320, which is invalid:

• expected dependent Bugzilla bug 1881522 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ASSIGNED instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

Bug 1969320: [release-4.7] packageserver CSV: add missing properties

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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: vrutkovs
To complete the pull request process, please assign njhale after the PR has been reviewed.
You can assign the PR to them by writing /assign @njhale in a comment when ready.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[timflannagan]

@vrutkovs Unfortunately, this repository is only set up to build downstream images for 4.8+ and 4.6/4.7 are still build upstream in the operator-framework organization. Do you want to open a PR against the release-4.7 branch in the upstream OLM repository when you get a chance?

/close

[openshift-ci]

@timflannagan: Closed this PR.

In response to this:

@vrutkovs Unfortunately, this repository is only set up to build downstream images for 4.8+ and 4.6/4.7 are still build upstream in the operator-framework organization. Do you want to open a PR against the release-4.7 branch in the upstream OLM repository when you get a chance?

/close

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.

[vrutkovs]

Sure thing, created operator-framework/operator-lifecycle-manager#2192