Namespaced servicebroker is a tech-review feature in v3.11
It uses 'automation-broker-apb' to install namespaced broker in a selected namespace regardless of whether cluster scoped ASB is installed.
According to your comments https://bugzilla.redhat.com/show_bug.cgi?id=1684036#c1
>The Operator had to change the names of how this was installed because the operator can install more than one broker.
If we still support the Namespaced servicebroker in v4.0 env, do you mean we need to use ASB operator to install the namespaced ASB?
If it is YES, we may need parameters such as '"broker_kind": "ServiceBroker/clusterservicebroker" in CR.
> Namespaced service broker is a tech-review feature in v3.11
Correct, and it is not a feature that we are moving forward with. It is my understanding that this is not something we need to fix because it was never supported and is not a feature that we want to work on.
The operator will not install a namespaced broker. It can install multiple cluster-wide brokers though.
If you need sign off from product management please ping Rob Szumski. Thanks!
Thank Shown for your reply.
I also need to confirm with you that when the feature of 'namespaced servicebroker' removed from v4.0, we should also remove image 'automation-broker-apb' in 4.0 image release list. This image is ONLY for 'install namespaced servicebroker' in v3.11.
If both of you and Shawn agree to remove the image from release list, I'll change the title to "remove image 'automation-broker-apb' from release list" .
Yes, you can go ahead and remove that image, as this isn't a feature we support in 4.0
'automation-broker-apb' should remove from release list, whether it needs any process to do it?
I keep the bug as assigned before your process done.
I changed component to Release, please correct me if I have mistake.
we have got confirmation from developer team and PM, hope remove image 'automation-broker-apb' from release list since it will not be supported in OCP4.0, detail info please refer comment 3, comment 4 and comment 5. Could you give me some support? Thanks.
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.