Christoph Stäbler

Should not be related to the openshift fork, as the manifests from upstreams are used

I could not reproduce the exact same behavior on 4.11.0-0.okd-2022-07-27-013906. When using the 0.72 manifests the operator pod comes up, but the handler pods don't. The issue with the handler...

/assign

/assign @nainaz /assign @zroubalik

Works for me. But we need to wait on the network manager fix and then the confirmation from QE

@ShaunaDiaz will you update https://docs.openshift.com/container-platform/4.11/networking/k8s_nmstate/k8s-nmstate-about-the-k8s-nmstate-operator.html too, that vSphere is supported? https://github.com/openshift/openshift-docs/blob/6a33d8303edf48af3068dc5fdae9369aef48f57d/networking/k8s_nmstate/k8s-nmstate-about-the-k8s-nmstate-operator.adoc#L14

I did the following steps and could not reproduce this in 1.8: * create a fresh kind cluster * install serving components and kourier (https://knative.dev/docs/install/yaml-install/serving/install-serving-with-yaml/#install-the-knative-serving-component) * install eventing components (https://knative.dev/docs/install/yaml-install/eventing/install-eventing-with-yaml/#install-knative-eventing)...

> Reopening since we decided to implement this as an experimental feature and there are followup tasks: > > * [x] Alpha: feature disabled by default. At this stage, Knative...

@Leo6Leo can you fix the unit test?

/assign