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
Tell us about your request
A configuration to allow ECS to deploy StatefulSets. I Want to maintain a sticky identity for each container within the Task . These containers are created from the same spec, but are not interchangeable: each has a persistent identifier that it maintains across any rescheduling.
Something basically like a StatefulSets equivalent of EKS in the ECS world.
Which service(s) is this request for?
ECS
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
Want to be able to create stateful applications using StateFulSets. So I want a predictable name for the containers generated from the TaskDefinition.
Are you currently working around this issue?
I'm deploying it in EKS as a K8s statefulSet resource
Community Note
Tell us about your request A configuration to allow ECS to deploy StatefulSets. I Want to maintain a sticky identity for each container within the Task . These containers are created from the same spec, but are not interchangeable: each has a persistent identifier that it maintains across any rescheduling. Something basically like a StatefulSets equivalent of EKS in the ECS world.
Which service(s) is this request for? ECS
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard? Want to be able to create stateful applications using StateFulSets. So I want a predictable name for the containers generated from the TaskDefinition.
Are you currently working around this issue? I'm deploying it in EKS as a K8s statefulSet resource
More Reading on this issue https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/