actions / actions/actions-runner-controller
Add TopologySpreadConstraints to Helm Chart
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 ability to define topology spread constraints in the values.yaml for actions-runner-controller configuration.
A clear and concise description of what you want to happen.
Note: Feature requests to integrate vendor specific cloud tools (e.g. awscli, gcloud-sdk, azure-cli) will likely be rejected as the Runner image aims to be vendor agnostic.
Why is this needed?
To have a better control on how the pods are scheduled and managed once deployed (can allow for higher uptime and reliability)
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The chart has an affinity variable already added. So I think it should be defined in a very similar manner.
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
Locate the Helm chart's values.yaml and the existing affinity setting, then trace how affinity is rendered into the runner pod specification. Follow that pattern for topology spread constraints and verify the rendered chart accepts the new values. Done means users can configure the constraints through values.yaml and they appear in the generated pod spec.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100