[Automated] Update eventing-istio-eventing nightly

[knative-automation]

/assign @knative-extensions/eventing-wg-leads
/cc @knative-extensions/eventing-wg-leads

Produced via:

for x in eventing-core.yaml eventing-crds.yaml in-memory-channel.yaml mt-channel-broker.yaml; do
  curl https://storage.googleapis.com/knative-nightly/eventing/latest/$x > ${GITHUB_WORKSPACE}/./third_party/eventing-latest/$x
done

Details:

[creydr]

/lgtm

[knative-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: creydr, knative-automation

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

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

[creydr]

/retest

[creydr]

/retest

[creydr]

/retest

[knative-prow]

New changes are detected. LGTM label has been removed.

[creydr]

log of current analysis:

• in control plane conformance tests of channel, we create a subscription for a channel named mychannelimpl. This subscription has as a subscriber uri http://example.com: https://github.com/knative/eventing/blob/bdca23daa788078b470a514a16f21363d820c580/test/rekt/features/channel/control_plane.go#L92 https://github.com/knative/eventing/blob/bdca23daa788078b470a514a16f21363d820c580/test/rekt/channel_test.go#L54
• later in the data plane conformance tests, we use the same channel name (mychannelimpl) and don't create a subscription for it in the failing test (channelAcceptsCEVersions()). Anyhow as the control plane tests run in the same namespace, we still have a subscription for this channel available. When we send a event to the channel, it tries to route it to the existing subscriptions subscriber (http://example.com), which results in a 502 (unable to complete request to http://example.com: unexpected HTTP response, expected 2xx, got 502).

Still not sure, why this only happens in eventing-istio and not in eventing-core tests too.

Update:
I think it is a combination of the changes from knative/eventing#7415 (async handler returned a 2xx when the event was accepted IIRC) and not deleting the resources correctly between control plane and data plane conformance tests (addressed in knative/eventing#7500).

[creydr]

🎉 🎉 🎉