actions / actions/actions-runner-controller
Allow specifying `volumes` and `volumeMounts` for the `actions-metrics-server` deployment
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?
The actions-runner-controller helm chart should allow specifying volumes and volumeMounts for the actions-metrics-server deployment.
Why is this needed?
Our use case is that we currently have our organisation CA certs mounted as additionalVolumes for the controller deployment itself. However, the actions-metrics-server is outputting x509 errors due to lacking said certs.
There could potentially be other use cases for adding volumes/volumeMounts to the actions-metrics-server, and it doesn't add much complexity.
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 by locating the Helm chart values and deployment template for the actions-metrics-server, then inspect how volumes are configured for the controller deployment. Render the chart with sample volume and volumeMount values and verify that both appear on the actions-metrics-server deployment, including support for the stated CA certificate use case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100