You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems to be trying update property azureDnsZone based on activity log, even though this property never changed, it succeeds and then tries to redo it again and again.
artisticcheese
changed the title
[Bug]:
[Bug]: Crossplane repeatedly tries to modify already existing resource when no changes are being made
Dec 16, 2024
I faced the same behavior for the KubernetesCluster and ApplicationGateway resources.
For the KubernetesCluster, the issue was because the provider detected drift for the api_server_access_profile (url) that I event didn't have defined in my MR definition.
I fixed it by adding:
When it comes to the ApplicationGateway the problem was with the probe block. I was missing match and minimumServers values there and because of that, the network provider was detecting the drift.
NOTE: What is interesting I tried to use both the managementPolicies without the 'LateInitialize' and the initProvider but both were not helping.
All these happen after the providers update from the version v1.5.1 to v1.11.0.
So lesion for me and for others is to double check the MRs after providers update and always use the DEBUG provider config to see what is the actual problem.
When it comes to the issue raised by the @artisticcheese , I also use the FrontdoorCustomDomain in my code base, but with BYO DNS, so not using the Azure DNS.
Is the dnsZoneId provided as a hardcoded string or it is passed during the composition reconciliation?
Is there an existing issue for this?
Affected Resource(s)
cdn.azure.upbound.io/v1beta1/FrontdoorCustomDomain
Resource MRs required to reproduce the bug
Steps to Reproduce
Applied resource
What happened?
CrossPlane consistently detects changes in resource even thought there are no changes based on logs in crossplane as well as in Azure
Relevant Error Output Snippet
Crossplane Version
1.18
Provider Version
1.10
Kubernetes Version
1.31.2
Kubernetes Distribution
AKS
Additional Info
It seems to be trying update property
azureDnsZone
based on activity log, even though this property never changed, it succeeds and then tries to redo it again and again.The text was updated successfully, but these errors were encountered: