Include must-gather image name in ENV

[black-dragon74]

The request for such feature came from a Bugzilla
for odf-must-gather.

We want the must-gather containers to be able to check the image being used. This is useful in cases where we want to deduce if the customer is using the image we ask them to.

While it is possible to call the k8s API internally (this is how it is implemented currently for odf-mg), it would be much efficient if the value is present inside the container as an ENV.

This patch sets an ENV var MUST_GATHER_IMAGE to reflect the image source of the pods.

Regards

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

[openshift-ci]

@black-dragon74: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/images	a02f9cf	link	true	/test images
ci/prow/verify	a02f9cf	link	true	/test verify
ci/prow/rpm-build	a02f9cf	link	true	/test rpm-build
ci/prow/security	a02f9cf	link	false	/test security
ci/prow/unit	a02f9cf	link	true	/test unit
ci/prow/build-rpms-from-tar	a02f9cf	link	true	/test build-rpms-from-tar
ci/prow/e2e-agnostic-ovn-cmd	a02f9cf	link	true	/test e2e-agnostic-ovn-cmd
ci/prow/verify-deps	a02f9cf	link	true	/test verify-deps

Full PR test history. Your PR dashboard.

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.

[black-dragon74]

PTAL @ardaguclu @soltysh

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale