run without the operator

[data-dude]

It would be nice to have an example of how to run this as just a deployment and not have to deal the operator

[lambdanis]

@data-dude You mean hubble-otel in a standalone mode instead of inside an OpenTelemetry collector? Or run OpenTelemetry collector but not using its operator?

[data-dude]

@lambdanis It would be nice to have a simple kubernetes deployment as an example as opposed to having to install opentelemetry operator and then installing opentelemetry collector. I ended up creating a deployment and then setting the config like below and added a configmap for my configuration. It's on a closed network so unfortunately i can't easily share right now.
It's my understanding the deployment should look similar to hubble ui. I think they are both getting data from the same source: hubble relay.

https://github.com/cilium/hubble-otel/blob/main/dev-scripts/run-otelcol.sh

IF you look at opentelemetry operator cluster roles you'll see it's exposing a lot of access to the cluster. I don't like that. hubble ui is able to get cilium events without needing to expose all those resources. For example one cluster role for opentelemetry gives it access to update or create configmaps throughout the entire cluster. Some of these operators are just ridiculous in how much access they need to the cluster.