kn-event sender image

[cardil]

Adding kn-event sender image

Requires merge of openshift/release#24476

[cardil]

/cc @mgencur

[mgencur]

Just for my understanding. Is the image used by the Serverless operator on server side? Isn't it something like e.g. our must-gather image which we produce but it's not mentioned in CSV because users will call it directly (on client side)?

[cardil]

When users will call kn event send --to giving some cluster local resource (like broker, channel or kservice), a K8s job will be created with this image.

It needs to be in CSV, in relatedImages section, to gets mirrored. So, the disconnected clusters will work as well.

/cc @rhuss

[cardil]

At @Kaustubh-pande: As you can see, the CSV generation mechanics in Serverless operator adds IMAGE_ to the front of the name of the image. In other places we have the same name but with _IMAGE as suffix instead.

WDYT of changing it in other places to this naming. In places like: https://github.com/openshift/knative-client/blob/f2b87473f6c69f413a2de69efeef82d51bf3c474/hack/build.sh.d/kn-plugin-event.sh#L7

[cardil]

/hold

Until image is available

[cardil]

After changes in openshift/release#24549 images was promoted properly:

$ skopeo inspect docker://registry.ci.openshift.org/knative/release-0.26:client-plugin-event-sender \
  | jq -r .Digest
sha256:4da4400a0c74d6d0fdd65d527c21bf5af187aa84d30de6d2dd593042fc1b7599

/unhold

[mgencur]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cardil, mgencur

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [mgencur]

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