Service Catalog should support User-Provided-Services in a more robust manner

[jberkhahn]

Service catalog should support User-Provided-Services, a concept where service instances and bindings can exist without a parent broker, class, or plan. This is used in the case where a user might have some pre-existing service that they wish to manage and use with the service-catalog lifecycle.

The current UPS broker is an ephemeral implementation that does not attempt to implement this capability in a reliable, reproducible manner.

One possible solution is allowing user's to manually create an instance with some sort of flag set marking the instance as UPS, and provide the creds that will be returned in the binding as an additional parameter.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[jberkhahn]

this is still a work in progress, but is put off until we get 0.2.0 out

[jberkhahn]

/dibs

[MHBauer]

/assign @jberkhahn

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[jberkhahn]

/lifecycle frozen