-
-
/kind bug
**What happened?**
Unable to use fargate for the efs-csi-controller:
```
│ Warning FailedScheduling 11m fargate-scheduler Pod not supported on Fargate: invalid SecurityContext f…
-
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the…
-
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the…
-
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the…
-
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the…
-
### What's the problem
Today [Amazon EKS supports running pods on AWS Fargate](https://github.com/aws/containers-roadmap/issues/32) in 8 regions: Virginia, Ohio, Oregon, Dublin, Frankfurt, Singapore,…
-
To get the logging working, I had to add the following the policy listed at [https://www.artillery.io/docs/load-testing-at-scale/aws-fargate#iam-permissions](https://www.artillery.io/docs/load-testing…
-
### What happened?
Surfaced in #1039. Our daily cron job fails about 33% of the time due to our Fargate tests.
The error from the test is:
```
utils.go:290:
Error Trace: /home/runn…
-
## Description
When repacking, `buildsys` attempts to cleanup the `buildsys-repack` container/image prematurely, printing the following error:
```shell
Error response from daemon: No such conta…