Mikołaj Świątek

I really like the concept of this test! Using the debug exporter and looking at otel container logs is simple, and lets us verify the SDK is emitting logs, if...

> * Certificates, in our e2e test we just install cert-manager > sounds like we would want to test for CSRs too then. Is that not covered in tests? Strictly...

This is clear if the Pod in question is new, but much less clear if it's an existing Pod being rescheduled. Reassigning targets is a fairly expensive operation for the...

#2528 didn't fix this, it just made the fix easier to implement. The main problem here is that it isn't clear to me what the behaviour should be like. I...

This is now fixed with https://github.com/open-telemetry/opentelemetry-operator/issues/3781 and https://github.com/open-telemetry/opentelemetry-operator/issues/3989.

@xuan-cao-swi thank you for the contribution! It's clear you put a lot of effort into it. That said, before we can proceed with code review, we'll need to discuss how...

I've added this point to the agenda for today's SIG meeting. Anyone interested is encouraged to join in on the discussion. You can find the calendar [here](https://github.com/open-telemetry/community?tab=readme-ov-file#calendar).

> I'm hoping an easy solution would just be to change the default of the MaxUnavailable: 1 to MinAvailable: 0 instead... code link: Does this not work? If you supply...

To be honest, what you're describing sounds like the right default behavior to me. The user pushes an invalid update, the collector stays in its pre-update state and an availability...

I don't think we currently want a feature in the operator that allows CRD defaults to be modified via operator configuration. In a lot of cases, this is effectively impossible...