actions / actions/actions-runner-controller
Allow TLS configuration for githubwebhookserver
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.5k
- Forks
- 1.5k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 27
Description
Is your feature request related to a problem? Please describe.
I would like to configure end to end TLS for the githubwebhookserver.
Describe the solution you'd like
I would like to have the githubwebhookserver listen for tls connections when configured with a host and certificate bundle secret name.
Describe alternatives you've considered
The only alternative I'm aware of is to terminate TLS at ingress.
There isn't much documentation around the githubwebhookserver so it's difficult to know what a typical configuration is or should look like. Browsing the code it doesn't appear that this feature is supported though.
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 githubwebhookserver implementation and its existing configuration, then review how host settings and certificate bundle secrets are represented. Check the current documentation and ingress-based TLS alternative first. Done means the server can be configured to accept TLS connections using the specified host and secret name.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, go, kubernetes
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100