-
Notifications
You must be signed in to change notification settings - Fork 108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Secret never Sync #1128
Comments
@daniel-maganto, thank you for raising this issue but I could not reproduce the issue with the provided information. Please check your example MR and let us know if there are other fields/parameters on the MR.
|
The provider's pods were stuck, after rebooting both, it started working successfully. It is funny because they were installed today so there is no overload at all |
It happens again, here the log traces.
|
I tried a few times and I can successfully create and delete the resource, but I can confirm that diff is detected in the logs:
@erhancagirici, do you have any idea about this? |
Hi, This looks like an issue with the custom diff function for handling |
Specific impact of this bug, as far as I can tell:
|
Is there an existing issue for this?
Affected Resource(s)
secretsmanager.aws.upbound.io/v1beta1 - Secret
Resource MRs required to reproduce the bug
Steps to Reproduce
Apply this resource in the cluster
What happened?
It never reach the state Sync: true
Relevant Error Output Snippet
Crossplane Version
1.14.5
Provider Version
1.0.0
Kubernetes Version
v1.28.2
Kubernetes Distribution
EKS
Additional Info
No response
The text was updated successfully, but these errors were encountered: