concourse / concourse/concourse-chart
Privileged flag for EKS Fargate launch profile
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 160
- Forks
- 189
- PR merge metrics
- No merged PRs in 30d
Description
Concourse workers can not launch from eks in fargate due to privileged: true
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:
https://github.com/concourse/concourse-chart/issues/60#issue-554781647
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with templates/worker-statefulset.yaml at the referenced security-context line, then read the discussion in issue #60. Determine whether the worker pod requires privileged mode for all tasks or only privileged tasks, and verify that the chart can support EKS Fargate without breaking the documented privileged-task behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100