support TLS when proxied

Bug #1815962 reported by Kevin W Monroe
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Docker Registry Charm
Fix Released
Low
Peter Jose De Sousa

Bug Description

The docker-registry charm does not pass TLS info over the website relation, hence things like haproxy cannot communicate with the registry via https.

If the registry has TLS configured, the update_reverseproxy_config function should pass that along to the proxy:

https://github.com/CanonicalLtd/docker-registry-charm/blob/master/reactive/docker_registry.py#L232

Changed in layer-docker-registry:
importance: Undecided → Low
status: New → Triaged
Changed in layer-docker-registry:
assignee: nobody → Peter De Sousa (pjds)
status: Triaged → Fix Committed
status: Fix Committed → In Progress
Revision history for this message
Peter Jose De Sousa (pjds) wrote :
Changed in layer-docker-registry:
status: In Progress → Fix Committed
Changed in layer-docker-registry:
status: Fix Committed → In Progress
Changed in layer-docker-registry:
status: In Progress → Fix Committed
Changed in layer-docker-registry:
milestone: none → 1.16
Changed in layer-docker-registry:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.