Thanks for great presentation. I have a question: Lets say i deploy a pod on eks fargate connected to 2 subnets, each subnet is in different availability zone. My question is, what happens in case of an AZ failure? Does the pod continue running, is it still accessible? Do resources running on EKS fargate continue working or recover in case if an AZ fails?
Hi Mihail. Try posting your question on our re:Post forum for more visibility and some helpful insight from our tech community. You can do so here: go.aws/aws-repost. ^BG
The Fargate nodes are AWS managed so there’s no need monitoring those. However if you mean application monitoring then you can run a sidecar container alongside your application containers for that
More than 3 years old but still great!
This is awesome walkthrough!
Fargate is a great product and I found this deep dive really useful, thank you.
Great detailed deep dive
Thanks for great presentation.
I have a question:
Lets say i deploy a pod on eks fargate connected to 2 subnets, each subnet is in different availability zone. My question is, what happens in case of an AZ failure? Does the pod continue running, is it still accessible? Do resources running on EKS fargate continue working or recover in case if an AZ fails?
Hi Mihail. Try posting your question on our re:Post forum for more visibility and some helpful insight from our tech community. You can do so here: go.aws/aws-repost. ^BG
nice, can we configure cloudwatch alarm in eks-fargate, do you have any article?
The Fargate nodes are AWS managed so there’s no need monitoring those. However if you mean application monitoring then you can run a sidecar container alongside your application containers for that