Unable to deploy eventing in different namespace because of hardcoded namespace #8407
Labels
good first issue
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
kind/bug
Categorizes issue or PR as related to a bug.
Describe the bug
Hi, it looks like its not possible to deploy and operate knative eventing in a different namespace using IMC because the service account is harded here:
https://github.com/knative/eventing/blob/main/pkg/apis/messaging/v1/in_memory_channel_validation.go#L29C7-L29C31
This const is afterwards used for the validation
checkSubsciberSpecAuthChanged
.I guess the best would be to use the SYSTEM_NAMESPACE env here in the
eventingControllerSAName
.Expected behavior
I can deploy knative eventing in any namespace and configure it properly
To Reproduce
The text was updated successfully, but these errors were encountered: