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
Hi Everyone !
We have installed crossplane with aws-provider in our EKS cluster and running aws-provider version 0.39.0 , and Crossplane version 1.10.1
We have created some lambda and statemachine claims which work fine on creation phase.
When we update the Claim for instance with new Location of Lambda Zip File or New StateMachine definition:
Everything get update on EKS side with needed updates.
It never sync the update to AWS actual resource
aws provider logs just log that the resource is up to date
2023-10-25T17:18:23.777Z DEBUG provider-aws Reconciling {"controller": "managed/function.lambda.aws.crossplane.io", "request": "/openphish-loader-ip-2gpr6-5tdn7"}
2023-10-25T17:18:23.877Z DEBUG provider-aws External resource is up to date {"controller": "managed/function.lambda.aws.crossplane.io", "request": "/openphish-loader-ip-2gpr6-5tdn7", "uid": "e8b09539-dda9-4090-a576-596047f989d3", "version": "58886252", "external-name": "ftb-dev-openphish-loader-ip-2gpr6", "requeue-after": "2023-10-25T17:19:23.877Z"}
Update when i describe the resouce in EKS it says it has not synced since creating time.
kubectl describe functions openphish-loader-ip-2gpr6-5tdn7 | grep -A10 Conditions:
Conditions:
Last Transition Time: 2023-09-27T23:03:17Z
Reason: Available
Status: True
Type: Ready
Last Transition Time: 2023-09-27T23:02:16Z
Reason: ReconcileSuccess
Status: True
Type: Synced
Events:
Anyone has encountred this ?
Am I running old version need to upgrade ?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi Everyone !
We have installed crossplane with aws-provider in our EKS cluster and running aws-provider version 0.39.0 , and Crossplane version 1.10.1
We have created some lambda and statemachine claims which work fine on creation phase.
When we update the Claim for instance with new Location of Lambda Zip File or New StateMachine definition:
Everything get update on EKS side with needed updates.
It never sync the update to AWS actual resource
aws provider logs just log that the resource is up to date
2023-10-25T17:18:23.777Z DEBUG provider-aws Reconciling {"controller": "managed/function.lambda.aws.crossplane.io", "request": "/openphish-loader-ip-2gpr6-5tdn7"}
2023-10-25T17:18:23.877Z DEBUG provider-aws External resource is up to date {"controller": "managed/function.lambda.aws.crossplane.io", "request": "/openphish-loader-ip-2gpr6-5tdn7", "uid": "e8b09539-dda9-4090-a576-596047f989d3", "version": "58886252", "external-name": "ftb-dev-openphish-loader-ip-2gpr6", "requeue-after": "2023-10-25T17:19:23.877Z"}
Update when i describe the resouce in EKS it says it has not synced since creating time.
kubectl describe functions openphish-loader-ip-2gpr6-5tdn7 | grep -A10 Conditions:
Conditions:
Last Transition Time: 2023-09-27T23:03:17Z
Reason: Available
Status: True
Type: Ready
Last Transition Time: 2023-09-27T23:02:16Z
Reason: ReconcileSuccess
Status: True
Type: Synced
Events:
Anyone has encountred this ?
Am I running old version need to upgrade ?
Beta Was this translation helpful? Give feedback.
All reactions