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
Seems that ECS Service if you are using a Taskdefinition without version (because you want to use always the latest) it always is trying to update reconcile the resources creating a infinite bucle.
What happened?
It creates a tons of calls to AWS Resources and even generate many reboots in ECS Provider pod.
The problem might be resolved when you reference a TaskDefinitionRef it resolves the TaskDefinition using: status.atProvider.family + status.atProvider.revision instead of only status.atProvider.family
Is there an existing issue for this?
Affected Resource(s)
service.ecs.aws.upbound.io/v1beta1
taskdefinition.ecs.aws.upbound.io/v1beta1
Resource MRs required to reproduce the bug
Steps to Reproduce
Seems that ECS Service if you are using a Taskdefinition without version (because you want to use always the latest) it always is trying to update reconcile the resources creating a infinite bucle.
What happened?
It creates a tons of calls to AWS Resources and even generate many reboots in ECS Provider pod.
Relevant Error Output Snippet
Crossplane Version
1.15.1
Provider Version
1.4.0
Kubernetes Version
v1.30.4-eks-a737599
Kubernetes Distribution
EKS
Additional Info
No response
The text was updated successfully, but these errors were encountered: