Open daniel-maganto opened 1 month ago
If it helps, checking the logs and behavior it seems that services always try to sync between the taskDefinition and can't.
I also updated to the latest version of the providers but got the same behavior.
apiVersion: ecs.aws.upbound.io/v1beta2
kind: Service
metadata:
[...]
spec:
forProvider:
taskDefinition: my-service-test
taskDefinitionRef:
name: my-service-test-dddddddddd
status:
atProvider:
[...]
taskDefinition: my-service-test:30
[...]
Is there an existing issue for this?
Affected Resource(s)
taskdefinition.ecs.aws.upbound.io/v1beta1
Resource MRs required to reproduce the bug
Steps to Reproduce
When you create the resource, if the ECS provider pod restarts due the error, it creates automatically another iteration of the task definition in an uncontrolled behaviour
What happened?
it creates automatically another iteration of the task definition in an uncontrolled behaviour
Relevant Error Output Snippet
Crossplane Version
1.15.1
Provider Version
1.4.0
Kubernetes Version
v1.29.4-eks-036c24b
Kubernetes Distribution
EKS
Additional Info
No response