You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: