Error after update dynatrace-operator update

[triceratops]

Hi Everyone

Has anyone else encountered this error after updating dynatrace-operator?

{"level":"info","ts":"2023-08-10T12:54:03.092Z","logger":"dynakube","msg":"could not reconcile component versions"}
runtime/asm_amd64.s:1598","ts":"2023-08-10T12:54:02.843Z"}{"error":"unable to retrieve auth token: invalid username/password: unauthorized: authentication required, visit https://aka.ms/acr/authorization for more information.","level":"error","logger":"dynakube","msg":"error reconciling DynaKube","name":"dynakube","namespace":"dynatrace","stacktrace":"unable to retrieve auth token: invalid username/password: unauthorized: authentication required, visit https://aka.ms/acr/authorization for more information.

Thanks in advance!

[dannemca]

It doesn't look like an error on the Dynatrace Operator it self but in your way to store the credential tokens (secrets).

Are you deploying the Operator following the default (from deploy dynatrace page) or did you customized it?

[triceratops]

i'm following the defaults

[benjamin_johnso]

Did you resolve this?

We are having the same problem (operator v0.12.0). It seems like the operator pod wants to query ACR for image information, but is unable to do so?

@Kulraj_Atwal 

[AskMe-Solutions]

My team have a same problem too. When update Dynatrace-Operator version 1.12.1

Anyone can resolve this?

@dannemca 

[shahinm]

This error occurs because of a missing custom pull secret in the dynakube.

In older versions of the operator, this error was ignored, and reconciliation continued since we trusted the node to be set up correctly so the image would be pullable. This is not the desired behavior since the Operator does not know which version is actually rolled out and can therefore not prevent downgrade and provide other benefits. Since v0.11.0 the operator supports token-based authentication, whereas before, it was only possible to use username/password-based authentication.

Moreover, with v0.12.x+, the Operator check is improved and must have the same custom pull secret as is configured on the node.

To solve the problem, add a custom pull secret to Dynakube and reapply the dynakube.

https://www.dynatrace.com/support/help/shortlink/dto-config-k8s#custompullsecret

[benjamin_johnso]

Hi - using the older operator, we are able to pull images & containers start fine, regardless of the operator log.

That means the node can pull the images - so we should be able to ignore or change this behaviour in the operator

[MaiAli]

Hi,

Have you fix it?
as I have the same issue when installing dynatrace operator 0.13.0

[ben_wrightson · Accepted solution]

Please use Operator v 1.0 or higher. That should solve the issue.