- Newest
- Most votes
- Most comments
It is consistent across the board on all clusters and there are no eviction errors.
We are not on a technical support tier, so I won't be opening a ticket to spend 1000 dollars on this issue.
First about the obvious - is this behavior universal cross the board? are all Fargate pods stuck at a lower version? If not, have you check and see if there are any eviction errors?
If as you suggested you recycle pod fairly frequently and you observed this issue consistently, I would recommend you submit a support ticket so our support engineers can take a deeper look.
In case anyone is looking for an answer some day: "We do not have an ETA on when we will migrate Fargate into kernel 5.x, but kubelet will have a faster and more frequent release cycle. the release cycle for minor versions on Fargate is slower than on EKS AMIs, hence the version might be behind, for example for 1.21, Fargate nodes are on 1.21.2 while EKS AMI is on 1.21.5. If there is a critical security vulnerability on a minor version of the kubelet, we do provision that release as soon as it is discovered, so rest assured that the changes between the minor versions are not critical or security related if there is a difference between both."
Relevant content
- asked 2 years ago
- asked 10 months ago
- asked a year ago
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
Sorry but lack of any insight into your account, it could be hard to give you specific directions. Fargate is supposed to update the AMIs, kubelet and agents automatically. It seems specifically the AMI is few versions behind. If your K8s versions are compatible (which it seems to be the case) the best approach is to get support to see if there is any service related issues. You will not be spending 1000 dollars on this. If you have an account team contact, please reach out to them too.