uselagoon / uselagoon/remote-controller
Rootless builds
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5
- Forks
- 2
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 5
Description
While working on https://github.com/amazeeio/lagoon/pull/2481 I noticed that the build pods are running as root. I just wanted to start a discussion about the best way to update them to run as a non-root user.
Do you see any issues with running as a different user? And where would be the best place to define a securityContext on the build pod? Hard-coding it in lagoon-kbd would be one way.. but is that the best way to go?
Contributor guide
No contributing guide indexed for this repository
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 by reviewing lagoon-kbd and the build-pod configuration involved in pull request 2481. Investigate where the build pod’s securityContext should be defined and assess the implications of changing its user. Done means an agreed approach for running build pods as non-root and a clearly identified configuration location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100