-
Notifications
You must be signed in to change notification settings - Fork 176
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Privileged flag for EKS Fargate launch profile #236
Comments
The workers always need In the future we're planning to create a k8s runtime which would not require privileged workers in your k8s clusters. concourse/rfcs#81 Another possibility is running containerd in rootless mode. We haven't experimented with this though. |
Concourse workers can not launch from eks in fargate due to
privileged: true
concourse-chart/templates/worker-statefulset.yaml
Line 64 in 8fe5b30
The following error is returned from fargate when trying to launch the pod:
Warning FailedScheduling <unknown> fargate-scheduler Pod not supported on Fargate: invalid SecurityContext fields: Privileged
Does this always need to run with privileged: true?
Or just by privileged tasks?
https://concourse-ci.org/jobs.html#schema.step.task-step.privileged
There is a another discussion regarding this flag here:
#60 (comment)
The text was updated successfully, but these errors were encountered: