Self-hosted runner registry
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 61
- Forks
- 91
- Avg merge
- 12d 10h
- Merged PRs (30d)
- 1
Description
There are many runner labels in use across the Kubeflow org but no document stating which labels exist, who owns them, what they have installed, or which are safe for pull_request from forks.
A new subproject cannot currently discover the full suite of available runners. The anti-pattern would be a new repo to copy label choice from existing repos without reason.
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 inventorying the runner labels used across the Kubeflow organization and reviewing the existing repositories that select them. Identify the owner, installed software, and fork pull-request safety for each label. Done means a maintained document covers the full available runner suite and explains how new subprojects should choose labels.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, devops, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100