Allow ServiceBinding generate Secret into multiple namespaces about sap-btp-service-operator HOT 3 CLOSED

I wonder whether they should share a single binding secret though and the request here should rather be allowing to create ServiceBinding resources in multiple namespaces that bind to a single ServiceInstance. ???

from sap-btp-service-operator.

@loewenstein Yes, they need to share the same ServiceBinding. This is how BTP works internally in relation to our BTP Subscription Tree. 

EDIT: It seems we "could" have a separate ServiceBinding with each microservice having its own set of credentials. However, in our case that would mean a significant amount of more configuration. It seems we have currently 37 service bindings, of which most are copied to multiple namespaces. So we'd have 150+ ServiceBinding resource definitions, should each microservice have its own, instead of sharing the secret of a single main ServiceBinding resource. I don't know if there's a limit to the number of BTP Service Bindings one can have.

If we started from scratch, maybe we could take that approach now that v0.5.2 allows ServiceBinding be defined in a different namespace than ServiceInstance, but at this time it'd require refactoring effort ..

You're damned if you do, you're damned if you don't.

from sap-btp-service-operator.

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days.

from sap-btp-service-operator.