cdi-operator updating cdi-apiserver all the time

[mhenriks]

Make sure TerminationMessagePolicy/Path are set when creating cdi-apiserver

Fixing regression introduced in #3465

What this PR does / why we need it:

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

Release note:

Make sure TerminationMessagePolicy/Path are set when creating cdi-apiserver

[mhenriks]

/cherrypick release-v1.60

[kubevirt-bot]

@mhenriks: once the present PR merges, I will cherry-pick it on top of release-v1.60 in a new PR and assign it to you.

In response to this:

/cherrypick release-v1.60

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.

[coveralls]

coverage: 59.331% (+0.08%) from 59.25%
when pulling ff403fd on mhenriks:fix-cdi-apiserver-event
into e4bc183 on kubevirt:main.

[mhenriks]

/test pull-containerized-data-importer-e2e-hpp-previous

[arnongilboa]

/lgtm

[akalenyu]

/approve

Nice catch, how does the error look like? I imagine lots of these messages?

containerized-data-importer/vendor/kubevirt.io/controller-lifecycle-operator-sdk/pkg/sdk/util.go

Line 156 in ff403fd

logger.Info("DIFF", "obj", objA, "patch", string(pBytes))

Should we try to write a functest for this? (could be outside this PR)

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: akalenyu

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 [akalenyu]

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

[kubevirt-bot]

@mhenriks: new pull request created: #3498

In response to this:

/cherrypick release-v1.60

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.