Allow to set registry mirrors
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 131
- Forks
- 65
- PR merge metrics
- No merged PRs in 30d
Description
Let's assume a scenario there network bandwidth is limited. And that there a local mirrors of public/private OCI regitries available.
It would be nice to be able to configure a list of registry mirrors for things like:
- HookOS to use locally mirrored images for tink-agent and actions
- oci2disc to use locally mirrored images
Using mirrors is much more convenient than using the edited image name of a locally published image. This makes it also possible to auto fallback to the original image registry when no mirrors are available.
I'm new to tinkerbell and also to go, but willing to contribute such features. So my question is, if that's even possibe with the current architecture of tinkerbell?
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
The issue names HookOS and oci2disc as the image consumers; start by tracing how each resolves and pulls tink-agent, action, and other OCI images. Check the current architecture and configuration paths before deciding whether mirrors can be shared. Done means a configurable mirror list works for both consumers and falls back to the original registry when mirrors are unavailable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- infrastructure, operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100