Add note regarding resource deletion

bricef · bricef · commit 493c562a0893 · 2018-12-11T12:40:17.000-08:00
diff --git a/README.md b/README.md
@@ -343,6 +343,10 @@ Noticeably, we don't manage Flux using Flux itself. This could easily get us in
 
 The commercial [Weave Cloud](https://www.weave.works/product/cloud/) agents will automatically update, by using a separate update path managed through a deployed service.
 
+**Automatically deleting services**
+
+Flux won't automatially delete services that are running on the cluster but don't exist in the control repository. While that might seem like a good idea at first, this would not allow Flux to be deployed to to existing clusters, as it would immediately delete all running deployments as soon as installed! Instead, you'll have to manually delete resources after removing them from the control repository.
+
 Further resources
 -----------------
 
