Several images are missing version tags

[curtbushko]

Problem

There are a couple images that are part of the release that are missing version tags and are only in the image registry as 'latest'.

Specifically, these ones are missing the v0.24.0, v0.22.2 etc tags

gcr.io/knative-releases/knative.dev/eventing/cmd/in_memory/channel_controller gcr.io/knative-releases/knative.dev/eventing/cmd/in_memory/channel_dispatcher gcr.io/knative-releases/knative.dev/eventing/cmd/mtchannel_broker

Not critical but it may help with debugging in the future

[antoineco]

This would certainly make it easier to reference release images indeed.

[lionelvillard]

maybe someone from the @knative/technical-oversight-committee knows how to fix it?

[dprotaso]

cc @chizhg from productivity

[github-actions[bot]]

This issue is stale because it has been open for 90 days with no activity. It will automatically close after 30 more days of inactivity. Reopen the issue with /reopen. Mark the issue as fresh by adding the comment /remove-lifecycle stale.

[pierDipi]

/remove-lifecycle stale /triage accepted

[takirala]

Tags are not published for following images:

console.cloud.google.com/gcr/images/knative-releases/global/knative.dev/eventing/cmd/mtchannel_broker console.cloud.google.com/gcr/images/knative-releases/global/knative.dev/eventing/cmd/in_memory/channel_controller console.cloud.google.com/gcr/images/knative-releases/global/knative.dev/eventing/cmd/in_memory/channel_dispatcher console.cloud.google.com/gcr/images/knative-releases/global/knative.dev/eventing/cmd/apiserver_receive_adapter

[ac-miller]

These images are still not being tagged. Is there any update on when tags will be created instead of relying on "latest"

[riqueps]

Image version tags is highly important for big companies where images should be tracked and stored inside the firm and also submitted to security scanning. In this cases latest tag is not allowed

Looking forward to have version tags.