eventing.knative.dev/scope: namespace does not work with distributed kafka channel

[AceHack]

Describe the bug
In the previous version eventing.knative.dev/scope: namespace would allow me to connect to different Kafka clusters at least at the namespace level.

Expected behavior
The ability to connect to more than one kafka cluster with knative.

To Reproduce
Add the eventing.knative.dev/scope: namespace to a kafka channel (distributed) and nothing happens.

Knative release version
nightly

Additional context
We don't absolutely need eventing.knative.dev/scope: namespace to work, we just need a way to connect to multiple kafka clusters, like maybe even specifying it at the KafkaChannel level similar to how it is in KafkaSource.

[lionelvillard]

Related to #157.

@AceHack assuming #157 gets resolved by allowing specifying the config at the KafkaChannel level, are you ok if we deprecate eventing.knative.dev/scope ?

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

[AceHack]

Any update?

[lionelvillard]

No progress I'm afraid. We are having discussions in #157 but nothing concrete yet.

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

[aliok]

/remove-lifecycle stale

[ssandanshi]

Any updates on this?

[lionelvillard]

/cc @travis-minke-sap

[travis-minke-sap]

Yeah, I hadn't seen this one in a long while ; ). Definitely something that we should support, and I don't see why the distributed implementation couldn't be made to work similar to consolidated version. My time is going to be focused elsewhere for awhile (#588, #613, etc...) but I've added to my personal internal tracking list of things that Eric and I can look at.

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

[travis-minke-sap]

/remove-lifecycle stale

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

[travis-minke-sap]

/remove-lifecycle stale

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.