Skip to content
This repository has been archived by the owner on Jan 28, 2020. It is now read-only.

Handle remote machineset deletion returning errors or taking a very long time #216

Open
csrwng opened this issue May 11, 2018 · 0 comments

Comments

@csrwng
Copy link
Contributor

csrwng commented May 11, 2018

If something goes wrong on the target cluster and the controller that handles remote deletions in the root cluster cannot successfully delete the remote machinesets, then we should either set some error status or give up trying to delete the remote machinesets and proceed with the rest of deprovisioning after a given amount of time.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant