Tyler Helmuth

Ok cool, this was my suspicion. I have no idea why the direct pod connections isn't working as expected, could be something unique to AKS setup. @jinja2 any ideas?

@jinja2 I am so glad you are part of this project because I don't know any of the networking/infra stuff you just said lol

We discussed this issue in the SIG meeting today. We decided we want the Spec to make a decision on `StateSet` before we'd move forward with any changes. I will...

There is also an open question on where this metric should live. @sirianni can you provide more details on the scaling issue you've experienced?

Reading through this issue again is there actually anything we need from the spec? This link (https://opentelemetry.io/docs/specs/otel/compatibility/prometheus_and_openmetrics/#stateset) feels like it is pretty clear about how we handle statesets in otel...

The issue is that both installations have the same name. You need to name your installs differently. As @JaredTan95 mentioned, this can be one with `nameOverride`.

@jaronoff97 FYI I'm not planning to look at this until you remove the `do-not-merge` tag

Instead of making this an option I'd be ok with switching to using Node IP in the preset instead of Node Name. I'm actually surprised we're using node name instead...

> It might be a breaking change for setups in which kubelet is not serving a certificate with the IP listed in subject alt name @jinja2 how common would this...

> Error: INSTALLATION FAILED: DaemonSet.apps "opentelemetry-collector-z9u7pzlfno-agent" is invalid: spec.template.spec.containers[0].env[2].valueFrom.fieldRef.fieldPath: Invalid value: "spec.hostIp": error converting fieldPath: field label not supported: spec.hostIp @alextricity25 looks like something with your use of the downward...