Description

Observed Behavior:

I created a Ressource with kro which is a kubernetes secret.
Kro is correctly creating the secret, but then it continuously find deltas in it and won't create the other resources

Expected Behavior:

I expect kro to see that there is no difference because the secret has been correctly created, and then it continue and create other resources.

Note: I didn't saw this behaviour in the 0.1 of kro.

Reproduction Steps (Please include ResourceGraphDefinition and Instances files):

Versions:

• kro version: 0.2
• Kubernetes Version (kubectl version): 1.30

Involved Controllers:

• Controller URLs and Versions (if applicable):

Error Logs (if applicable)**: This is the log line but in better readibility

Pod: kro-6d5b8f8b8f-7zxt9
Application: kro
Timestamp: 2025-02-04T10:31:08.327Z
Log Level: DEBUG
Component: controller.eksclusters
Message: Found deltas for resource

Resource Details:
{
    "namespace": "workload-cluster3",
    "name": "workload-cluster3",
    "resourceID": "argocdSecret",
    "delta": [
        {
            "path": "stringData",
            "desired": {
                "config": {
                    "awsAuthConfig": {
                        "clusterName": "workload-cluster3",
                        "roleARN": "arn:aws:iam::798082067117:role/workload-cluster3-argocd-role"
                    },
                    "tlsClientConfig": {
                        "caData": "LS0tLS1CRUdJTiBDRVJUSUZ....[truncated]....FLS0tLS0K",
                        "insecure": false
                    }
                },
                "name": "workload-cluster3",
                "server": "https://2D0E5C77B3C.truncated.4553EA49070B.gr7.us-west-2.eks.amazonaws.com"
            },
            "observed": null
        }
    ]
}

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Which option describes the most your issue?

No response