Messaging storage v1

[aliok]

Fixes #3583

Proposed Changes

• Make messaging.* v1 resources the stored version
• Add those resources to migration job

Release Note

- 🧽 Update or clean up current behavior
Change storage versions of flows.* resources from v1beta1 to v1:
          - "channels.messaging.knative.dev"
          - "inmemorychannels.messaging.knative.dev"

action required: You must run pre-install job prior to upgrading to get messaging.* resources to v1 API.

Docs

No docs change necessary. The content at https://knative.dev/docs/install/upgrade-installation/#run-pre-install-tools-before-upgrade is good enough

[aliok]

/hold

I thought all resources' reconcilers are updated to use v1 shape, but subscription reconciler isn't.

Let me exclude subscriptions in this PR

[aliok]

/unhold

Excluded subscriptions.

Created this ticket to track things: #3929

[nlopezgi]

can we just add the groups and resources here to LOC 48 and 50?

[aliok]

@nlopezgi you mean messaging api group should come before eventing api group? or something else?

[nlopezgi]

I think it should be possible to have a single apiGroups statement that includes the following resources:

      - "containersources"
      - "sinkbindings"	      
      - "channels"
      - "inmemorychannels"
      - "brokers"
      - "triggers"	

given that for all resources the same verbs are listed?
Just to reduce a bit of verbosity, but in all senses a nit, so totally your choice to leave as is or collapse.

[aliok]

@nlopezgi not sure if that would work. These resources are from different apiGroups (eventing, messaging, etc.).
Let's leave as is and we can have a look later?

[nlopezgi]

thanks! yeah, you are probably right. I think with #3943 my concern is addressed

[nlopezgi]

small nit, feel free to resolve or leave as is if you think its cleaner. Otherwise
/lgtm

[matzew]

/lgtm
/approve

[knative-prow-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aliok, matzew

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

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

[nlopezgi]

/lgtm