actions / actions/actions-runner-controller
github-webhook-server manafest with release
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?
A manifest outside of helm for github-webhook-server
Why is this needed?
All things helm should also be in a manifest with the release.
Additional context
Adding github-webhook-server after the fact, if not using helm, is almost impossible.
Also, the labels across deployments should match and not be inconsistent. I am having a hell of a time trying to pull all the github-webhook-server objects out of a kube managed by Helm so I can make a manifest.
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
Review the existing Helm resources for github-webhook-server and the release packaging first, identifying every object and its labels. Done means a standalone manifest is shipped with the release, reproduces the Helm deployment, and uses consistent labels across deployments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- infrastructure, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100