Create consensus on unbind about service-catalog HOT 8 CLOSED

Sounds reasonable. Related to this is the entire discussion of how 'status' is represented in our resources - status vs conditions, etc. The topic Brian brought up.

from service-catalog.

A similar concern exists for deprovision -- finalization of Instance is needed to support accepting a delete request and then having the service catalog controller take actions to ensure the deprovision is done for the Instance before it is ultimately deleted.

from service-catalog.

Has a decision been made on what happens to existing Bindings when a deletion/finalization is made on an Instance?

Sent from my iPhone

On Nov 19, 2016, at 18:52, Paul Morie [email protected] wrote:

A similar concern exists for deprovision -- finalization of Instance is needed to support accepting a delete request and then having the service catalog controller take actions to ensure the deprovision is done for the Instance before it is ultimately deleted.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

from service-catalog.

if the delete on the instance is allowed to happen (due to it still being used) then I would think all bindings for that instance would be deleted too.

from service-catalog.

@arschles

Has a decision been made on what happens to existing Bindings when a deletion/finalization is made on an Instance?

Not at all. I'm about to create an issue for it. I think this falls under 'deprovision'.

from service-catalog.

Edited out the 'deprovision' bits of this issue -- spinning into a new issue.

from service-catalog.

Background on the finalization pattern: https://github.com/kubernetes/kubernetes/blob/master/docs/design/namespaces.md#example-openshift-origin-managing-a-kubernetes-namespace

from service-catalog.

We have since agreed on finalization and how the controller should handle this.

from service-catalog.