[main] Use Broker's own configmap for Kafka

[mgencur]

Fixes an issue with using wrong default values when config-br-defaults configmap points to another cluster-default configmap that might not include configuration for Kafka. It might include for example MTChannelBasedBroker configuration in which case the Broker creation fails with an error like this

invalid configuration - numPartitions: 0 - replicationFactor: 0 - bootstrapServers:  - ConfigMap data: map[channelTemplateSpec:apiVersion: messaging.knative.dev/v1
        kind: InMemoryChannel
        ]

Proposed Changes

• Creation a new ConfigMap in the test namespace that will be used by the Brokers.

Release Note

Docs

[codecov]

Codecov Report

Merging #1591 (eb7fe21) into main (25dec98) will increase coverage by 0.04%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##               main    #1591      +/-   ##
============================================
+ Coverage     74.87%   74.92%   +0.04%     
- Complexity      595      597       +2     
============================================
  Files           116      116              
  Lines          4211     4211              
  Branches        171      171              
============================================
+ Hits           3153     3155       +2     
+ Misses          802      799       -3     
- Partials        256      257       +1     

Flag	Coverage Δ
java-unittests	81.90% <ø> (+0.10%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
...dispatcher/impl/consumer/BaseConsumerVerticle.java	93.75% <0.00%> (+6.25%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 25dec98...eb7fe21. Read the comment docs.

[knative-prow-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mgencur, pierDipi

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

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

[pierDipi]

/cherry-pick release-0.26

[knative-prow-robot]

@pierDipi: once the present PR merges, I will cherry-pick it on top of release-0.26 in a new PR and assign it to you.

In response to this:

/cherry-pick release-0.26

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[pierDipi]

/cherry-pick release-1.0

[knative-prow-robot]

@pierDipi: once the present PR merges, I will cherry-pick it on top of release-1.0 in a new PR and assign it to you.

In response to this:

/cherry-pick release-1.0

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[knative-prow-robot]

@pierDipi: new pull request created: #1592

In response to this:

/cherry-pick release-0.26

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[knative-prow-robot]

@pierDipi: new pull request created: #1593

In response to this:

/cherry-pick release-1.0

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.