Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1543129 - Installer needs a way to configure the local registry adapter for additional projects, more than just 'openshift'
Installer needs a way to configure the local registry adapter for additional ...
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Service Broker (Show other bugs)
3.7.0
x86_64 Linux
low Severity medium
: ---
: 3.11.0
Assigned To: Dylan Murray
Zihan Tang
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2018-02-07 14:21 EST by Wolfgang Kulhanek
Modified: 2018-10-11 03:20 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-10-11 03:19:09 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:2652 None None None 2018-10-11 03:20 EDT

  None (edit)
Description Wolfgang Kulhanek 2018-02-07 14:21:49 EST
Description of problem:

For the Template Service Broker there is a configuration variable that allows adding more than just the 'openshift' project to the search scope of the template service broker:

openshift_template_service_broker_namespaces=['openshift','templates']


We need the same capability for the Ansible Service Broker. It isn't quite feasible to store every apb in the 'openshift' project.
So something like:

ansible_service_broker_local_registry_namespaces=['openshift','apb']

We already have whitelists as a configuration option:
ansible_service_broker_local_registry_whitelist=['.*-apb$']

So adding the namespaces/projects should be a next logical step.

Ideally we could specify something like '*' or 'ALL' to make both brokers search all namespaces the way templates work in OCP versions <3.7.

Version-Release number of the following components:
3.7.23

How reproducible:
Always
Comment 1 Dylan Murray 2018-08-08 14:06:30 EDT
For now I am going to expose a new var `ansible_service_broker_local_registry_namespaces` which is a list of namespaces that can be used and defaults to ['openshift`]. 

+1 to the idea of specifying "*" and having the broker search all namespaces it has access to. Since this will be a more involved change and outside the scope of the installer I will create a separate bug for that.
Comment 3 openshift-github-bot 2018-08-10 10:33:00 EDT
Commits pushed to master at https://github.com/openshift/openshift-ansible

https://github.com/openshift/openshift-ansible/commit/bf2c042dc08786377fd31644f050bb6d4eb5eb95
Bug 1543129 - Add configuration option for ASB local registry namespaces

https://github.com/openshift/openshift-ansible/commit/728b2be34cc82799ec4c62fd7893cea9b0aaa0ae
Merge pull request #9485 from dymurray/namespaces

Bug 1543129 - Add configuration option for ASB local registry namespaces
Comment 5 Zihan Tang 2018-08-30 05:53:04 EDT
Verified.
openshift-ansible-3.11.0-0.25.0

when set : 
ansible_service_broker_local_registry_namespaces=['openshift','apb']

the openshift registry will be : 
  - type: local_openshift
    name: localregistry
    white_list: []
    namespaces: [openshift, apb]

and asb pod starts successfully.
Comment 7 errata-xmlrpc 2018-10-11 03:19:09 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:2652

Note You need to log in before you can comment on or make changes to this bug.