Project

General

Profile

Actions

Bug #28698

closed

docker registry in katello doesn't work with installed pulp3

Added by Justin Sherrill almost 5 years ago. Updated almost 5 years ago.

Status:
Closed
Priority:
Normal
Category:
Container
Target version:
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

Currently katello expects the smart proxy pulpcore.yaml to contain:

content_app_rul: http://localhost/24816

And then podman pull communicates like this:

podman ----> katello ----> pulp_content_app

There is a desire to not have katello know about or communicate directly with teh content app, so the communication needs to look like this:

podman ---> katello ---> apache ---> pulp_content_app

Right now, all auth ends at katello, so we will need apache to authorize katello to talk to the pulp_content_app registry. We can use an ssl cert to do this.

Actions #1

Updated by The Foreman Bot almost 5 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/Katello/katello/pull/8499 added
Actions #2

Updated by The Foreman Bot almost 5 years ago

  • Fixed in Releases Katello 3.16.0 added
Actions #3

Updated by Justin Sherrill almost 5 years ago

  • Status changed from Ready For Testing to Closed
Actions #4

Updated by Chris Roberts almost 5 years ago

  • Target version set to Katello 3.15.0
  • Triaged changed from No to Yes
  • Fixed in Releases Katello 3.15.0 added
  • Fixed in Releases deleted (Katello 3.16.0)
Actions

Also available in: Atom PDF