Add in-memory-channel to enable eventing release

[mchmarny]

Eventing release was failing for me due to missing ClusterChannelProvisioner

unable to recognize "https://github.com/knative/eventing/releases/download/v0.4.0/release.yaml": no matches for kind "ClusterChannelProvisioner" in version "eventing.knative.dev/v1alpha1"

Adding https://github.com/knative/eventing/releases/download/v0.4.0/in-memory-channel.yaml fixes this

Fixes #(issue-number)

Proposed Changes

[evankanderson]

I think this should be applied to all the "install" documents (e.g. -with-AKS, -custom-install, etc).

Do you want to do that, or should I?

[samodell]

Thanks for pointing that out! I can go ahead and make the change across the rest of the install files, @evankanderson

[evankanderson]

/lgtm

[samodell]

/lgtm
/approve

[knative-prow-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mchmarny, samodell

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 [mchmarny,samodell]

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

[samodell]

Hey @mchmarny -- I dug into this a bit more; if you installed eventing from release.yaml, then it would have come bundled with the in-memory channel provisioner. @evankanderson confirmed that still holds true in 0.4, so we don't need to add a command for explicitly installing the in-memory channel provisioner. Sounds like you may have installed from eventing.yaml instead, which doesn't come with the in-memory channel provisioner.

[mchmarny]

ust followed the instructions here ```shell kubectl apply --filename https://github.com/knative/serving/releases/download/v0.4.0/serving.yaml \ --filename https://github.com/knative/build/releases/download/v0.4.0/build.yaml \ --filename https://github.com/knative/eventing/releases/download/v0.4.0/in-memory-channel.yaml \ --filename https://github.com/knative/eventing/releases/download/v0.4.0/release.yaml \ --filename https://github.com/knative/eventing-sources/releases/download/v0.4.0/release.yaml \ --filename https://github.com/knative/serving/releases/download/v0.4.0/monitoring.yaml \ --filename https://raw.githubusercontent.com/knative/serving/v0.4.0/third_party/config/build/clusterrole.yaml ``` Without the highlighted line, that command results in error ```shell unable to recognize "https://github.com/knative/eventing/releases/download/v0.4.0/release.yaml": no matches for kind "ClusterChannelProvisioner" in version "eventing.knative.dev/v1alpha1" ``` Seems to be reproducible on a brand new cluster.

[samodell]

Hmm -- @evankanderson I know you double-checked that release.yaml does include the in-memory channel provisioner, so... any idea what's going on here?