This message was deleted.

If there is a single property you can’t match, you can use

ignoreChanges

on that property to allow the adoption to proceed (which will then also avoid trying to replace the cluster after you adopt it). That said - what exactly is the resource/property that causes the problem here?

the property is the clientSecret. I tried every version of a secret, from configuration to even hardcoded value. Nothing will match. So then it tries to update the secret, which fails. I will try to ignore it. ~ servicePrincipal: { + clientSecret: "[secret]" }