Mikołaj Świątek
Mikołaj Świątek
That does sound like something we should fix. I recall trying to make it work the way you describe when adding support for Probes and ScrapeConfigs, but then I don't...
If the CRD isn't present in the cluster, we shouldn't emit any errors about it. I'm not sure how easy this is going to be in practice, as we use...
Turns out this is something we do ourselves [here](https://github.com/open-telemetry/opentelemetry-operator/blob/main/cmd/otel-allocator/internal/watcher/promOperator.go#L192). Detecting if a CRD is present is a solved problem because the operator does it [here](https://github.com/open-telemetry/opentelemetry-operator/blob/main/internal/autodetect/main.go#L66). So this shouldn't be too...
Sorry for not reviewing this earlier @ChristianCiach. Your changes look good to me, in general. Something that only became clear to me once I saw this PR, though, is that...
@ChristianCiach apologies for the late response. We've had a lot of long vacations and other life events among the maintainers as well recently, so we're not as prompt in responding...
@ChristianCiach how about using `[]v1beta1.AnyConfig`, the same as we do for [scrape configs](https://github.com/open-telemetry/opentelemetry-operator/blob/6f0c57d46c7e5c64447baf62bc6b4c7bc4982445/apis/v1alpha1/targetallocator_types.go#L79) embedded in the target allocator? The size of the CRD is a concern, and I, for one,...
@ImDevinC are you able to reproduce this issue in an empty kind cluster? If it's the same issue as @alorenzo175 experienced, then the fix should be straightforward, but that can...
I'd be fine with a fix that increases the duration on the CA certificate or changes the renew period. It's not clear this is the root cause of the problem...
Deleting the certs should cause the operator to recreate them.
We might need to look at the secret values for the certificates then. In particular the target allocator cert and the CA cert, since that's where the error is coming...