Actions
Bug #28696
closed
with pulp3 installed on a main katello server, apache should be configured to help serve docker content
Difficulty:
Triaged:
No
Description
The following configuration needs to occur in order for katello to properly connect to the content app serving a docker registry:
<Location /pulpcore_registry/v2/>
SSLRequire %{SSL_CLIENT_S_DN_CN} eq "admin"
</Location>
ProxyPass /pulpcore_registry/v2/ http://127.0.0.1:24816/v2/
ProxyPassReverse /pulpcore_registry/v2 http://127.0.0.1:24816/v2
Note, that this requires this PR to actually work in katello https://github.com/Katello/katello/pull/8499
The idea behind this change is that katello will use its own pulp client certs to authenticate with the /pulpcore_registry/ endpoint which will require a signed cert with a CN of 'admin'. It will then proxy the request through to the pulp content app
Updated by Justin Sherrill about 5 years ago
- Subject changed from pulp3_content_url in pulp3 foreman-proxy config should point to internal content app to with pulp3 installed on a main katello server, apache should be configured to help serve docker content
Updated by Ewoud Kohl van Wijngaarden about 5 years ago
- Blocks Tracker #28736: Use Pulp 3 for File and Container content in Katello added
Updated by The Foreman Bot about 5 years ago
- Status changed from New to Ready For Testing
- Assignee set to William Clark
- Pull request https://github.com/theforeman/puppet-foreman_proxy_content/pull/233 added
Updated by William Clark about 5 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset puppet-foreman_proxy_content|c30fa19981386ae1a66adabd8ce767410c24000d.
Actions