Don't explicitly mention that saving annotations is critical

Signed-off-by: Nic Cope <nicc@rk0n.org>
This commit is contained in:
Nic Cope 2024-01-31 12:27:21 -08:00
parent 26c4ff4957
commit c0dbc0f5cf
1 changed files with 3 additions and 4 deletions

View File

@ -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 * `crossplane.io/external-create-failed` - The last time the provider failed to
create the resource. create the resource.
Use `kubectl get` to view the annotations on a managed resource. For example, an Use `kubectl get` to view the annotations on a managed resource. For example, an
AWS VPC resource: 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 provider creates it. Instead the external system generates an nondeterministic
name and returns it to the provider. name and returns it to the provider.
When the external system generates the resource's name, it's critical that the When the external system generates the resource's name, the provider attempts to
provider saves it to the managed resource's `crossplane.io/external-name` save it to the managed resource's `crossplane.io/external-name` annotation. If
annotation. If it doesn't, it leaks the resource. it doesn't, it _leaks_ the resource.
A provider can't guarantee that it can save the annotation. The provider could 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 restart or lose network connectivity between creating the resource and saving