Operator is constantly pushing UPDATE calls without making any changes? about opentelemetry-operator

[jaronoff97]

It looks like its specifically for the monitoring service, are there any operator logs you can share? CC @iblancasa who was working on this recently.

[diranged]

It looks like its specifically for the monitoring service, are there any operator logs you can share? CC @iblancasa who was working on this recently.

I put the operator into debug mode - and there were zero relevant logs.. just lots of spam about the PDB not being created, nothing else useful.

[LaikaN57]

It looks like its specifically for the monitoring service [...]

@jaronoff97 This is actually happening on all otel services. OP was posting an example of one of the UIDs affected. Sorry for the confusion here.

Query:

fields @timestamp as ts, objectRef.name as name, objectRef.resourceVersion as ver, responseObject.metadata.resourceVersion as reqVer, requestObject.metadata.resourceVersion as rspVer, @message as msg
| filter @logStream like "kube-apiserver-audit"
| filter verb = "update"
| filter objectRef.resource = "services"
| filter user.username = "system:serviceaccount:otel:operator"
| sort @timestamp desc

Results:

[iblancasa]

It looks like its specifically for the monitoring service, are there any operator logs you can share? CC @iblancasa who was working on this recently.

I have been reviewing and I don't see what of the recent changes I did can produce this effect. I will be happy to help in any way. I'll try to reproduce it.

[diranged]

It looks like its specifically for the monitoring service, are there any operator logs you can share? CC @iblancasa who was working on this recently.

I have been reviewing and I don't see what of the recent changes I did can produce this effect. I will be happy to help in any way. I'll try to reproduce it.

Thank you - and if there's any need for us to run a test-build of the operator that enables any kind of debug logs, we're happy to do that..