actions / actions/actions-runner-controller
Missing `hostPID` and `hostNetwork` fields in Pod Spec
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.5k
- Forks
- 1.5k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 27
Description
What would you like added?
I'm working with eBPF, and my tests require the hostPID and hostNetwork fields to perform certain tasks on the host machine.
Why is this needed?
As far as I understand, the Pod Spec doesn't contain these two fields.
So, I would like to request the addition of these two fields to the Pod Spec. If you approve, I can open a pull request to contribute this change.
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 at apis/actions.summerwind.net/v1alpha1/runner_types.go around line 94 and inspect the Pod Spec definition. Check how this repository updates API types after changing that definition. The work is done when the Pod Spec exposes both hostPID and hostNetwork for runner configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100