Joel Takvorian

@vietj I suggested to add at least this one more example : https://github.com/eclipse-vertx/vertx-tracing/pull/6/files

So what's the recommended solution? (other than installing a dependency full of vulnerabilities?)

PS: I saw this issue that could be similar: https://github.com/operator-framework/operator-sdk/issues/5773 , but since symptoms seem different, I opened a new one

Found a workaround, inspired by https://github.com/operator-framework/operator-sdk/issues/5946 Using `--index-image` pointing to my operator-sdk cli version worked: ```bash operator-sdk run bundle quay.io/netobserv/network-observability-operator-bundle:v0.1.3 --index-image quay.io/operator-framework/opm:v1.22 operator-sdk run bundle-upgrade quay.io/netobserv/network-observability-operator-bundle:v0.1.4 ```

I had the same issue. I've been able to make it work quite easily, keeping using `systemd-resolved`. Since I already had CRC installed at some point on my client laptop,...

FWIW here's a descriptive XML from ovs: https://github.com/openvswitch/ovs/blob/master/ofproto/ipfix.xml I'm trying to understand, for this issue with ovs to be fixed (ie. Enterprise format not being supported with goflow and breaking...

I could make it work "partially" with ovs, standard fields are now recognized and collected ; there's not only the enterprise number parsing missing, but also variable length fields [1]...

To give some context, I'm working on Kiali. The first thing that comes to my mind is that we often query not just a single rate value aggregated over a...

For the record here's broadly the kind of thing I could imagine for metrics / graph adapters as a custom resource: ```yaml // Adapter title that could be used for...

Hi @michelleN @grampelberg , We discussed a little bit about that a couple of months ago ( https://github.com/deislabs/smi-spec/issues/43 ) but TBH there hasn't been much time spent here on our...