Eventing install from release.yaml fails without also installing in-memory channel provisioner

[samodell]

Expected Behavior

When you install Eventing from https://github.com/knative/eventing/releases/download/v0.4.0/release.yaml, the in-memory channel provisioner should be included.

Actual Behavior

Users are seeing errors when installing eventing from https://github.com/knative/eventing/releases/download/v0.4.0/release.yaml unless they explicitly install the in-memory channel provisioner from: https://github.com/knative/eventing/releases/download/v0.4.0/in-memory-channel.yaml

Steps to Reproduce the Problem

1. Try to install https://github.com/knative/eventing/releases/download/v0.4.0/release.yaml without in-memory channel provisioner
2. Get error, as shown in comments on PR Add in-memory-channel to enable eventing release #944 and Fix knative installation for Gardener #960

[bbrowning]

Looking at the last error from #944, this looks to be because we're both defining and trying to create an instance of the ClusterChannelProvisioner custom resource in the same yaml file.

This error from @mchmarny on #944 confirms that:

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"

So, it's not that the in-memory provisioner is not listed in the release yaml. Rather, it's that there's a race condition in our release yamls just like we've had with Istio where you need to first define the CRDs before creating instances of those CRDs.

[samodell]

Thanks @bbrowning ! I'll clarify that in the install docs.

[tarunrathor-pro]

When can we get the updated installs docs. I am facing the same problem

[samodell]

Hey @tarunrathor-pro -- this issue should be fixed by simply re-running the commands.

[tarunrathor-pro]

@samodell I am referring to https://github.com/knative/docs/blob/master/install/Knative-with-GKE.md
Should i re-run the following commands again to recover from this error

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

[samodell]

Yep, @tarunrathor-pro , rerun those.

[tarunrathor-pro]

@samodell
I retried as suggested and even after retry i see following messages

clusterrole.rbac.authorization.k8s.io/knative-serving-build created
unable to recognize "https://github.com/knative/eventing/releases/download/v0.4.0/in-memory-channel.yaml": no matches for kind "ClusterChannelProvisioner" in version "eventing.knative.dev/v1alpha1"
unable to recognize "https://github.com/knative/eventing/releases/download/v0.4.0/in-memory-channel.yaml": no matches for kind "ClusterChannelProvisioner" in version "eventing.knative.dev/v1alpha1"
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"
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"

The output of
`$ kubectl -n knative-eventing get po

NAME READY STATUS RESTARTS AGE
eventing-controller-6554f9cbcf-lfs92 1/1 Running 0 111m
in-memory-channel-controller-7888dfffd7-k5b4c 1/1 Running 7 122m
in-memory-channel-dispatcher-56d6f99dc6-k4rzm 2/2 Running 2 122m
webhook-654b696b9b-gklqm 1/1 Running 0 111m`

[bbrowning]

@tarunrathor-pro In the specific command you're running, you need to kubectl apply the yaml for the eventing release BEFORE applying the yaml for the in memory channel.

[craigbox]

I had this problem too installing 0.4.

To fix the docs, we just need to swap the order?

--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 \

becomes

--filename https://github.com/knative/eventing/releases/download/v0.4.0/release.yaml
--filename https://github.com/knative/eventing/releases/download/v0.4.0/in-memory-channel.yaml \

?