Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support deleting of resources? Yes/No #3

Open
rspurgeon opened this issue Aug 26, 2020 · 0 comments
Open

Support deleting of resources? Yes/No #3

rspurgeon opened this issue Aug 26, 2020 · 0 comments

Comments

@rspurgeon
Copy link
Contributor

It's debatable if the ccloud-operator sub-component of this project should support deleting of Confluent Cloud resources. It's common for automated resource management tools to support this feature very carefully, and not by default (see Flux).

Maybe most common operational design patterns will involve migrating to newly named resources instead of hard deletes. If that's the case, the value of delete is reduced and may not outweigh the risk.

For POC use cases with Confluent Cloud, it's an easy operation to delete an entire environment resulting in a trivial cleanup for disposable experiments with this project.

Various opinions welcome here.

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

No branches or pull requests

1 participant