fix broken in-mem channel namespace mode

[lionelvillard]

Fixes #4844

Proposed Changes

• Fix privilege escalation error
• Fix missing env vars in namespace-scoped in-mem dispatcher.

Release Note

:bug: Fix bug preventing the namespace-scoped in-memory channel to become ready. 

Docs

[codecov]

Codecov Report

Merging #4906 (bd2e963) into master (4e5bdf9) will increase coverage by 0.49%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #4906      +/-   ##
==========================================
+ Coverage   81.14%   81.63%   +0.49%     
==========================================
  Files         294      294              
  Lines        8383     8393      +10     
==========================================
+ Hits         6802     6852      +50     
+ Misses       1175     1135      -40     
  Partials      406      406              

Impacted Files	Coverage Δ
...inmemorychannel/controller/resources/dispatcher.go	100.00% <100.00%> (ø)
pkg/apis/flows/v1/parallel_validation.go	100.00% <0.00%> (+100.00%)	⬆️
pkg/apis/flows/v1beta1/parallel_validation.go	100.00% <0.00%> (+100.00%)	⬆️

---

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 4e5bdf9...bd2e963. Read the comment docs.

[n3wscott]

where did CONTAINER_NAME come from?

[lionelvillard]

5f66209#diff-793cc23b5cb3cde6c57ad48d4e44b3252912e0e14ea50abb32fbd3904b053846

[lionelvillard]

/test pull-knative-eventing-integration-tests

[lionelvillard]

/test pull-knative-eventing-integration-tests

[vaikas]

/lgtm
/approve
/hold
in case @n3wscott has more questions.

[knative-prow-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vaikas

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

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

[n3wscott]

/unhold
Sorry, I was just having a driveby question

[pierDipi]

/cherry-pick release-0.21
/cherry-pick release-0.20

[knative-prow-robot]

@pierDipi: new pull request created: #5029

In response to this:

/cherry-pick release-0.21
/cherry-pick release-0.20

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

[knative-prow-robot]

@pierDipi: #4906 failed to apply on top of branch "release-0.20":

Applying: fix broken in-mem ns mode
Using index info to reconstruct a base tree...
M	pkg/reconciler/inmemorychannel/controller/resources/dispatcher.go
M	pkg/reconciler/inmemorychannel/controller/resources/dispatcher_test.go
Falling back to patching base and 3-way merge...
Auto-merging pkg/reconciler/inmemorychannel/controller/resources/dispatcher_test.go
CONFLICT (content): Merge conflict in pkg/reconciler/inmemorychannel/controller/resources/dispatcher_test.go
Auto-merging pkg/reconciler/inmemorychannel/controller/resources/dispatcher.go
CONFLICT (content): Merge conflict in pkg/reconciler/inmemorychannel/controller/resources/dispatcher.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 fix broken in-mem ns mode
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-0.20

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.