We still use docker-registry.tools.wmflabs.org in plenty of places.
However, in T306039: Decision request - Toolforge external infrastructure domain usage we decided to move forward with using svc.toolforge.org for this kind of FQDNs.
This task is to track the work to introduce docker-registry.svc.toolforge.org.
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| toolforge: docker-registry: enable HTTP endpoint for svc.toolforge.org | operations/puppet | production | +8 -0 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | taavi | T306039 Decision request - Toolforge external infrastructure domain usage | |||
| Open | None | T366453 toolforge: introduce docker-registry.svc.toolforge.org FQDN to replace docker-registry.tools.wmflabs.org |
Change #1038227 had a related patch set uploaded (by Arturo Borrero Gonzalez; author: Arturo Borrero Gonzalez):
[operations/puppet@production] toolforge: docker-registry: enable HTTP endpoint for svc.toolforge.org
Change #1038227 abandoned by Arturo Borrero Gonzalez:
[operations/puppet@production] toolforge: docker-registry: enable HTTP endpoint for svc.toolforge.org
Reason:
no longer interested
This change triggered a discussion about the security of the Cloud VPS openstack network, the potential for network sniffing, and nova-proxy, given the fact that it doesn't support HTTPS backend.
Given this is just a cosmetic change, I lost interest, and wont be making it.