Closed zqzzq closed 4 years ago
@zqzzq Thanks for the report. Do you have any pods in the test
namespace?
From a quick look my guess is that you have installed the MT Broker but the default broker is configured to use ChannelBroker: See the default broker annotation: eventing.knative.dev/broker.class: ChannelBasedBroker
And I don't see 'broker-controller' running in knative-eventing. So, for this particular broker you can change the BrokerClass to MTChannelBasedBroker So, if you do kubectl -n test edit broker default
And change this annotation: eventing.knative.dev/broker.class: ChannelBasedBroker
to this: eventing.knative.dev/broker.class: ChannelBasedBroker
it should work.
And for any future brokers, you should probably update your ConfigMap to something like this so that they will get the correct BrokerClass annotation: https://knative.dev/docs/eventing/mt-channel-based-broker/
kind: ConfigMap
apiVersion: v1
metadata:
name: config-br-defaults
namespace: knative-eventing
data:
default-br-config: |
clusterDefault:
brokerClass: MTChannelBasedBroker
apiVersion: v1
kind: ConfigMap
name: imc-channel
namespace: knative-eventing
@vaikas thank you very much! The default broker becomes ready according to your suggestion, closing this.
Great to hear!! 👍
sigh, I had made a typo in the original instructions, but looks like despite this oversight you figured it out :) For future references it should have said:
And change this annotation:
eventing.knative.dev/broker.class: ChannelBasedBroker
to this:
eventing.knative.dev/broker.class: MTChannelBasedBroker
Describe the bug A clear and concise description of what the bug is. label the ns:
but the broker is not ready:
my pod in knative-eventing:
Expected behavior A clear and concise description of what you expected to happen. the default broker becomes ready To Reproduce Steps to reproduce the behavior.
Knative release version v0.14.1 Additional context Add any other context about the problem here such as proposed priority