Skip to content
This repository has been archived by the owner on May 6, 2022. It is now read-only.

Policy for handling broker deletion and deprovision #481

Closed
arschles opened this issue Mar 6, 2017 · 10 comments · Fixed by #2711
Closed

Policy for handling broker deletion and deprovision #481

arschles opened this issue Mar 6, 2017 · 10 comments · Fixed by #2711
Assignees
@mszostok
Labels
broker-api-spec-compliance
Milestone
1.0.0

Comments

@arschles
Copy link
Contributor

arschles commented Mar 6, 2017

At our last face-to-face meeting in late January 2017, we discussed what the system should do on a broker deletion and deprovision operation.

On a deprovision operation, we decided that the default case is to fail the deprovision if there are bindings against the instance being deprovisioned. A "force" or "cascade" flag can be explicitly set on the call to make all bindings be unbound, and then the deprovision be done.

We decided on a similar strategy for broker deletion.

This issue is for discussing how we are going to achieve this functionality in kubectl. The CLI provides a --cascade and --force flag that we should consider utilizing for this purpose.
@arschles arschles added this to the MVP 2 milestone Mar 6, 2017
@pmorie pmorie modified the milestones: MVP 3, MVP 2 Mar 13, 2017
@pmorie pmorie modified the milestones: 0.0.3, 0.0.2 Apr 6, 2017
@pmorie
Copy link
Contributor

pmorie commented Apr 6, 2017

Not going to be in 0.0.2

@arschles
Copy link
Contributor Author

Moving out of a milestone until we decide what to do here.

@arschles arschles removed this from the 0.0.3 milestone Apr 13, 2017
@ash2k ash2k mentioned this issue Jul 1, 2017
Closed
@duglin duglin added this to the 1.0.0 milestone Jul 9, 2017
@duglin
Copy link
Contributor

duglin commented Jul 9, 2017

Added 1.0.0 since we need to decide before v1.

@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 21, 2019
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 21, 2019
@jberkhahn jberkhahn removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label May 23, 2019
@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 21, 2019
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Sep 20, 2019
@mszostok
Copy link
Contributor

/remove-lifecycle rotten

@k8s-ci-robot k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Sep 20, 2019
@mszostok
Copy link
Contributor

/assign

@mszostok
Copy link
Contributor

we started working on that, see: kyma-project/kyma#5180

more details will be presented soon

@piotrmiskiewicz piotrmiskiewicz mentioned this issue Sep 24, 2019
Merged
@mszostok mszostok mentioned this issue Oct 21, 2019
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@mszostok mszostok

Labels
broker-api-spec-compliance
Projects
None yet
Milestone
1.0.0
Development

Successfully merging a pull request may close this issue.

Cascading binding deletion piotrmiskiewicz/service-catalog
7 participants
@arschles @pmorie @duglin @jberkhahn @mszostok @k8s-ci-robot @fejta-bot