From c0dbc0f5cf6ce980374bf38e8b564d12cb085a7d Mon Sep 17 00:00:00 2001 From: Nic Cope Date: Wed, 31 Jan 2024 12:27:21 -0800 Subject: [PATCH] Don't explicitly mention that saving annotations is critical Signed-off-by: Nic Cope --- content/master/concepts/managed-resources.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/content/master/concepts/managed-resources.md b/content/master/concepts/managed-resources.md index 458fc4bd..14684d1b 100644 --- a/content/master/concepts/managed-resources.md +++ b/content/master/concepts/managed-resources.md @@ -653,7 +653,6 @@ Providers set three creation annotations to avoid and detect leaked resources: * `crossplane.io/external-create-failed` - The last time the provider failed to create the resource. - Use `kubectl get` to view the annotations on a managed resource. For example, an AWS VPC resource: @@ -681,9 +680,9 @@ Some external systems don't let a provider specify a resource's name when the provider creates it. Instead the external system generates an nondeterministic name and returns it to the provider. -When the external system generates the resource's name, it's critical that the -provider saves it to the managed resource's `crossplane.io/external-name` -annotation. If it doesn't, it leaks the resource. +When the external system generates the resource's name, the provider attempts to +save it to the managed resource's `crossplane.io/external-name` annotation. If +it doesn't, it _leaks_ the resource. A provider can't guarantee that it can save the annotation. The provider could restart or lose network connectivity between creating the resource and saving