Document upstream Docker Hub configuration for clusters without Docker Hub access
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7
- Forks
- 2
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 3
Description
Summary
We need documentation covering how to configure upstream Docker Hub when clusters cannot reach Docker Hub directly (e.g., air-gapped environments, restricted egress, corporate firewalls).
Context
Customers in restricted environments need to pull container images that would normally come from Docker Hub through an alternative path (private registry mirror, pull-through cache, etc.). We've done this before but the process isn't documented, making it hard for customers or field engineers to set up independently.
Requested Content
- How to configure a registry mirror or pull-through cache as a Docker Hub upstream
- Any PTD-specific configuration needed (e.g.,
ptd.yamlsettings, cluster spec fields) - How product images and runtime images are affected
- Example configurations for common setups (ECR pull-through, Harbor mirror, etc.)
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 locating the ptd.yaml settings and cluster spec fields related to registries, then review existing documentation for product and runtime image configuration. Document registry mirrors or pull-through caches for restricted clusters, including ECR pull-through and Harbor examples, and explain how both image categories are affected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100